You are referring to section 5.2.1 if I am not correct, not 3.2.1? The context is important here. 5.2.1 is discussing using the variable as part of your local.conf. Which is a different animal then ad

Signed-off-by: Jeremy Puhlman <jpuhlman@...> --- .../findutils/{findutils_4.6.%.bbappend =3D> findutils_%.bbappend} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename recipes-extended/f

Signed-off-by: Jeremy Puhlman <jpuhlman@...> --- conf/layer.conf | 2 ++ .../recipes-devtools}/python/files/sitecustomize.py | 0 .../python2-layer/recipes-devtools}/python/python_%.bbappend | 0

Signed-off-by: Jeremy Puhlman <jpuhlman@...> --- .../files/misc_create_inode.c-label_rootfs.patch | 20 ++++++++++++++------ 1 file changed, 14 insertions(+), 6 deletions(-) diff --git a/recipes

It is. You more or less just need to figure out which layer the recipe comes from. Then you can build functions on top of that. https://github.com/MontaVista-OpenSourceTechnology/meta-montavista-cgx/b

From: "Jeremy A. Puhlman" <jpuhlman@...> --- meta-cgl-common/conf/layer.conf | 2 +- meta-cgl-fsl-ppc/conf/layer.conf | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/meta-cgl-

Given it is looking for libMyTool.so and not a versioned library, my guess is that the shared library is not setting a proper soname when being built. All libraries should be built with a soname, and

Was the change to the directory structure release for 2.3.2 intentional. All the other releases are under: http://downloads.yoctoproject.org/releases/yocto/yocto-<release version> where as 2.3.2 is ht

This basically concatenates qemu to what ever is already in BBMASK. It is a regex expression so you want to treat it as such. You want to likely do something like: BBMASK .= "|(qemu)" OTOH, qemu match

Not necessarily best practice, but it is something that bitbake has supported. If you create a directory under myapplication_1.0 that is unique and not an override, you can specify the directory name

Because the package list has PN at the end by default: PACKAGES="${@bb.utils.contains('PTEST_ENABLED', '1', '${PN}-ptest', '', d)} ${PN}-dbg ${PN}-staticdev ${PN}-dev ${PN}-doc ${PN}-locale ${PACKAGE_

I was working with some layerinfo code, and I noticed that the value of BBFILE_COLLECTIONS in layer.conf in the meta-intel repo are kind of all over the map: for each in */conf/layer.conf; do cat $eac