Hi, I would fork linux-libc-headers to the kernel you are actually using despite the comment in the file. That's the only way to export headers from the correct kernel to everyone who needs them. Ther

Sounds like yocto could fit to your needs well. My personal experiences summarized: Pros with yocto: * configuration of everything is possible * BSP support available for various SoC's and boards * op

One possibility is to provide these keys as host native tools and data to build of target recipes. This makes the files available in the build environment but does not expose them to target. Create a

Hi, Only clean way to do this is to split the recipe into two parts: * native for the build time tooling * target for the target only build, which depends on the native build time tooling Everything e

Hi, Hmm, good that same patches are already in master branch but I somehow got a much older master branch state from remote git://git.yoctoproject.org/meta-selinux commit a917c322c120c05fc6746fc9aca38

With latest poky master, glib-2.0-native fails to compile: | meson.build:1:0: ERROR: Value "false" for combo option is not one of the choices. Possible choices are: "enabled", "disabled", "auto". Thus

Looks good! Reviewed-by: Mikko Rapeli <mikko.rapeli@...>

Hi, Depends on your HW platform, kernel version etc, but one possible solution is installing rng-tools binary package which starts rngd at boot. See http://lists.openembedded.org/pipermail/openembedde

Should be: IMAGE_NAME := "${IMAGE_BASENAME}-${PV}-${DATETIME}" note the added $. I guess that's the bit which confuses bitbake. Been there, done that too :) Hope this helps, -Mikko

Ok, that too then. Then all hope is lost so lets include sed there as well :) We're ramping up with ptests and will provide fixes back to upstream. All this work is very much appreciated here in downs

GNU sed does not come from coreutils but from sed recipe. Your call in the end. I just provided my point of view. Understood. I hope you could also add 'set -eux' to all ptest shell scripts. Many of t

Please no. I'm running images without sed and using busybox sed instead, and that doesn't support -u. I'd rather be compatible with sed from busybox to keep changes to images minimal (e.g. install of

Thanks for this useful summary of tools. I use buildhistory a lot. It contains recipe, binary package, image and SDK metadata. Many of the queries and tools you mentioned can be 'git grep'ed from buil

Hi, From my experience, what CMAKE_BUILD_TYPE means varies between SW components. Thus I think the current approach of not setting it is correct. SW components must set their own defaults in either CM

At least on x86 targets, it's available from gcc-runtime recipe and libstdc++-staticdev binary package on sumo/yocto 2.5 and later. -Mikko