Hi, What about: pkg_postinst_ontarget_${PN}() { : } in your bbappend? This should effectively override the task from a bbappend (except if there are _append for the task). Can't comment on this being

#yocto

Hi, IIUC, SSTATE_MIRRORS is just a way to prepopulate your local sstate-cache. So you'd need to have SSTATE_MIRRORS="" but also change SSTATE_DIR to some path where no sstate-cache is so that the loca

Hi Gary, I'm not sure setup.py is supported for the project as it's empty? So distutils does not look correct to me. You have a makefile (inherit no classes, that;s the default) or Cmakelists (inherit

#yocto

Hi Pankaj, packagegroup-core-x11-server is a recipe (well, both a recipe and a package) not a feature. If you want to add packagegroup-core-x11-server package to your image, you need to add it to IMAG

#yocto

Hi Pankaj, Missing x11 in DISTRO_FEATURES in your distro. http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-graphics/packagegroups/packagegroup-core-x11-xserver.bb?h=master#n12 (I also

#yocto

Hi Pankaj,

#yocto

bitbake rrdtool -e and look for the line starting with PACKAGECONFIG. CHeck it's set to what you want, if not, look the lines above to understand why it's not set "correctly". Quentin

Hi, You have probably added core-image-sato to DEPENDS which is incorrect. You can't add an image recipe as a dependency. Quentin

#raspberrypi #yocto

Hi Stephan, Libraries and binaries are stripped of the debug symbols before adding them to the "normal" package. The version with the debug symbols are usually in the -dbg package of your recipe. You

#devtool

Hi Tomek, Because there is a misunderstanding on how _<override> works :) KERNEL_MODULE_AUTOLOAD_velismate += "A" KERNEL_MODULE_AUTOLOAD += "B" does not mean that you add A in case of velismate machin

Hi, _append in most cases require a leading space, i.e. you want: DISTRO_FEATURES_append = " pam" Let us know if that fixes it. Quentin

#yocto

Hi Damien, It is? https://git.busybox.net/busybox/tree/findutils/find.c#n206 You need to enable it in busybox config (you can use config fragments IIRC). layers.openembedded.org is your friend. For ex

Hi Ayoub, BBPATH[1] is what's used to locate bbclasses. It's defined in your conf/layer.conf. You can either make sure your layer is parsed before the one having the original systemd.bbclass (in BBLAY

FWIW, you could make the parsing order not matter (at least in thud, from a quick look, master as well). LAYERSERIES_COMPAT is resolved after all layer.conf have been parsed[1]. I do not know if it's

Hi Damienm Conceptually, no. An image recipe is a recipe. Global data is global and local data is local. A recipe (image or package) set local data only. Correct way is different distro or machine. Ob

On Wed, May 13, 2020 at 09:53:12AM -0400, Robert P. J. Day wrote: [...] > > it gets weirder ... the project i'm working with is based on morty > so that variable *would* still be relevant, but even ad

That'll teach me to check in master instead of my release of Yocto :) Quentin

Hi Robert, I'm not sure, but there might be a need to add it to SRC_DISTRIBUTE_LICENSES in openembedded-core/meta/conf/licenses.conf. Quentin

Hi Robert, You can add a license to your layer by doing the following in conf/layer.conf: LICENSE_PATH += "${LAYERDIR}/licenses" and in there you put the Unlicense file named exactly the same with the

Hi Mohamed, Why? What's the exact use case? Maybe you could play with PREMIRROS? (I've never explicitly used that variable though): https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.htm