what you are looking at is feeds area, where the format will vary depending upon which online package management is in use. So you will have to make that differentiation. Packages file is used when

Hello, It's a bit hard to know where to start without more information. Can you tell us what release, layers and hardware you are using? Are you able to reproduce the problem using runqemu ? Are you

One more question: plain-text files named 'Packages' and placed during distribution build in subtrees tmp/deploy/rpm, .../ipk, ... are these artifacts supported YP releases can still build?

Hi, Anyone else encounter this? WARNING: cve-update-db-native-1.0-r0 do_populate_cve_db: Failed to fetch CVE data ([SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get

In the YOCTO/Linux source tree there's drivers/spi/ which has all the source for SPI drivers. There's only 1 file, spidev.c, which has: static int __init spidev_init(void) { int status;

Two projects are given. They use different YP release each. Projects use also different target platform each. I wonder if differences in structuring metadata- and recipes- directory tree

... snip ... you can't legitimately expect support for YP 2.0, which is six years old and has been EOLed for quite some time. rday

How are the odds for this question to get more audience on stackoverflow? In meantime I tried to search release notes of all YP releases starting the oldest used here for related entries. Unsure if it

There are 2 git repos: openembedded-core and meta-openembedded. openembedded-core has oe-init-build-env to create the build environment. meta-openembedded has the recipe for spidev-test If I use

Hello all, I need two specific way to halt my embedded Linux system. The first halt mode is used to halt the system while maintaining watchdog trigger. The second halt mode is used to halt the system

Thats codename for 3.3 Signed-off-by: Armin Kuster <akuster808@...> --- conf/layer.conf | 2 +- meta-hardening/conf/layer.conf | 2 +-

Hi, I want to create a text file containing a list of all the source files used to build my Yocto image. Is there any mechanism to do that? I found out that archiever.bbclass creates a sub-folder

in current OE, there is no "GPL-2.0" license file, there is "GPL-2.0-only" and "GPL-2.0-or-later" and a bunch of others, so i think you need to pick one of those. rday

I tried to build spidev-test using the bitbake recipe: spidev-test.bb I set: ARCH=arm BBPATH CROSS_COMPILER=arm-linux-gnueabihf- PATH ... and then tried to build spidev-test: $ bitbake -b

Hi Mauro, oe-pkgdata-util lookup-recipe qtwebkit could help. Or if you know which file you don't want in your fs and want to know which package is installing it: oe-pkgdata-util find-path

Hello, This is about two projects Projects A and B. Both use Yocto to build embedded-Linux distribution. However different Yocto release each. Also different target platform each. One puts Linux

Hi all.I need to find which recipe installs qtwebkit in my final image. I look in on every recipes I make but I don't find who put qtwebkit in my image. I have the same matter with *-dev packages I

I'm 'bitbaking' now.

Yocto Technical Team Minutes, Engineering Sync, for March 16, 2021 archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit == disclaimer == Best efforts are made

It appears that the upstream directory layout changed, so this is also an issue in master. A patch has been submitted to resolve the issue and I will cherry-pick it to dunfell after it appears in