Hi Stephen, I think you may need to inherit pkgconfig class too if your cmake relies on this to find packages. Cheers, Quentin

Hi Hassan, I believe the issue is that the Makefile is not in your `S` directory. You can run `pwd` in do_install and check where the Makefile is relative to this path and update S to point to this or

Hi, It seems it is only available in langdale and master (mickledore) branch in meta-raspberrypi layer, c.f. https://layers.openembedded.org/layerindex/recipe/327281/ It is also called rpi-libcamera-a

Hi Trevor, s/R2S/R4S/ Cheers, Quentin

Hi Murali, bbappends are appending content to already existing recipes. There are two possible issues, for chromium_%.bbappend, no chromium recipe is found in the included layers, make sure the layer

Hi Matt, Except because of a personal preference of having things spatially separated, it doesn't make much sense to me. When you're building for multiple machines, some sstate-cache is shared. Such i

Hi Matt, What are you trying to do? Which problem are you trying to solve that would require this? It depends what exactly you want to do, because this would apply only to SSTATE cache for the recipes

Hi Konstantin, So, you needed the extra :beaglebone-yocto because the machine configuration file is parsed after local.conf, therefore since beaglebone-yocto.conf file has: MACHINE_EXTRA_RRECOMMENDS =

Hi Ron, The package.manifest only contains packages so it's normal that lsusb does not appear there since there's no package *named* lsusb. E.g. there's no lsusb package in Debian, but you can install

Hi Ferry, Just to add that bitbake now supports pressure thresholds (since Kirkstone release I believe): https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-user-manual-ref-variables.htm

Hi Konstantin, This makes sense, I'll send a patch updating the documentation to reflect this change. I thought we already had discussed about this and someone sent a patch but doesn't seem so :/ No.

Hi Iggy, Please keep the mailing list in copy. You tell Yocto to build for a specific MACHINE (this is the name of the variable) either from the command line when calling bitbake or in your local.conf

Hi Iggy, You are building for a specific machine (MACHINE in your local.conf or via command line argument for example), so Yocto definitely knows it. Then your machine configuration file (the one in t

Hi Martin, As far as I remember, RDEPENDS is handled by the package manager when installing the package. So I imagine this is a way to make sure that a filesystem is not built with two packages that a

#bitbake

Hi Sébastien, The logic seems reasonable to me, yes. We could have used the deploy directory instead and depend on the do_deploy task instead of the do_populate_sysroot but I think it is actually safe

#kirkstone

Hi Trevor, Reviewed-by: Quentin Schulz <foss+yocto@...> Thanks, Quentin

Hi Maik, Development vs production is solved by using different distros. You can then have the same recipe but with different files (see (DISTRO)OVERRIDES mechanism for SRC_URI file:// files, c.f. htt

Hi all, Gentle ping. Cheers, Quentin

Hi Jason, Sorry for the delay, your mail got lost in my pile of to-answer that never slims down apparently. I just tested on Kirkstone release, yocto-4.0.4 tag. It works as expected. Did you end up fi

Hi Mauro, Can you try ;subdir= parameter? c.f. https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-user-manual-fetching.html#the-unpack Cheers, Quentin