Fellow Developers, I am attempting to add gdb to a Yocto project based on Yocto 2.3 (Pyro). The build complains about a missing libreadline.a.

this is best course of action, for maintainance POV as well as readability, I know of custom packages that bundled bits and pieces into a single package like this and call it some meta package but

Hello, I am building SDK for Windows host using meta-mingw (bitbake image -c populate_sdk). That SDK will be given to customer and it should be self-contained - contain all binaries required to

Hello, I am building SDK (bitbake image -c populate_sdk). Those SDK binaries will be given to customer. How can I generate license manifest file (open source disclosure)? I can see *.manifest files

Hi Mauro, all, During the creation of the rootfs of your image yocto will try to install both packages, and should complain loudly because the same file is provided by two packages. There are a few

do_install() is not installing things into the final image. It is installing items to the target location under a separate 'destination directory', independently of anything else that installs to the

Hi all. I'm Mauro. I have to resolve this matter. The recipe  init-ifupdown.bb install file interfaces in /etc/network. I build a library which need to install the same file in the same

Worked, thank you! Mit freundlichen Grüßen / Best regards, Kevin Kettinger Am 05.06.2020 um 08:53 schrieb Denys Dmytriyenko:

bitbake package-index

Hello, i want to use my yocto build sever as opkg package source for updating some packages directly, but it seems after generating an image the "Packages" file for opkg is not created. In the

Hello, The Warrior branch of Poky has had its last official dot release. It will be moving to Community support and EOL within 6 weeks if no one steps up. If someone is interested in taking on the

Backport 2 patches to fix the build errors on Fedora 32. Fixes: [snip] ../cil/src/cil_verify.lo:(.bss+0x4f0): multiple definition of `CIL_KEY_CONS_T3'; ../cil/src/cil_verify.lo:(.bss+0x4f8): multiple

Yes, the kernel is typically provided by the BSP vendor through the BSP layer, and they define the kernel version in use. The security concerns still apply though: if there is a vulnerability in their

Thanks Alexander, When you say "The versions of libraries and tools are not independent from Yocto versions, in fact they are directly defined through oe-core metadata that is in a specific Yocto

The versions of libraries and tools are not independent from Yocto versions, in fact they are directly defined through oe-core metadata that is in a specific Yocto version. For examples, what version

My question is about the #Yocto update and maintenance strategy. I have several projects for different boards and different versions of Yocto (1.7 2.0 2.2) which includes their BSP. As an OS build

Hi Zheng, there is a ML for SWUpdate and meta-swupdate (see CC), we are cross-posting here: openSSL is not the only supported SSL library, the Webserver runs also with mbedTLS. This patch forces to

-c -o mongoose/mongoose.o mongoose/mongoose.c | mongoose/mongoose.c:4496:10: fatal error: openssl/ssl.h: No such file or directory Signed-off-by: Zheng Ruoqing <zhengrq.fnst@...> ---

I retract my question and apologize for being an idiot… Apparently somewhere along the line while I wasn’t paying attention, the entirety of that upstream git repo got pulled into our local

what code did you merge and was it into layers? or your app. autoreconf helping would mean that its some pre-generated header etc. I am not sure what was causing it and not sure what fixed it