Hi There is an old discussion regarding this in this link: https://lists.frrouting.org/pipermail/frog/2019-January/000445.html But I can't find any updated one. Is there an updated recipe to build

Hi To get a value of some variable added in recipe it is best to use bitbake with `-e` flag which should print the whole environment, then one can just use `grep` to search for given variable. Let

Hi There is a variable (or what ever it's called) inside a recipe. I want to know its value. I've used `bbnote "something"` but this gives a parse error. How to properly log?

This email is a follow-up from the session held on Friday at the OpenEmbedded Developer's Virtual Meeting (see https://www.openembedded.org/wiki/OEDVM_Nov_2021) The session was not recorded, but the

rootfs-postcommands.bbclass says: # Perform any additional adjustments needed to make rootf binary reproducible rootfs_reproducible () { if [ "${REPRODUCIBLE_TIMESTAMP_ROOTFS}" != "" ]; then

After doing a bit of bisecting it appears that this commit is the culprit: reproducible_build: Remove BUILD_REPRODUCIBLE_BINARIES

Hello, I've been working on extending SPDX SBOMs for SDKs. In poky/meta/classes/create-spdx.bbclass I added: do_populate_sdk[recrdeptask] +=

All, The below were the owners of enhancements or bugs closed during the last week! Who Count michael.opdenacker@... 1 Grand Total 1 Thanks, Stephen K. Jolley Yocto Project Program

All, Below is the list as of top 46 bug owners as of the end of WW49 of who have open medium or higher bugs and enhancements against YP 3.5. There are 99 possible work days left until the final

All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on

Hi, We use build image-buildinfo class: https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#ref-classes-image-buildinfo Just add INHERIT += "image-buildinfo" to your local.conf to

Hi, We set the BUILDNAME (via local.conf) variable to the output of "git describe --long --always" so this info ends up in /etc/version instead of a date. (i.e to know the exact source version of the

Hello everyone, This is the full report for yocto-3.4.1.rc1: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults ======= Summary ======== No high

Hello, I'm trying to run an existing image (based on Gatesgarth) on a Celeron 6305E NUC. The application running on this image is a media player which uses Gstreamer for decoding and displaying

merged. thanks armin

Hello, I'm having some issue moving from an HDMI display to a USB display. I figure out that I needed to enable these parameter in the kernel to use the USB

The usual solution is for the recipe to allow building native and you install the tools from that recipe for the target recipe to use. The better solution is that the source knows how to build host

Hi all, I have what I believe is a basic question yet I cannot find any definitive answer: is it possible for a target recipe (e.g. u-boot or barebox) to provide a native tool (i.e. mkimage) for the

Agreed, I poorly reviewed it. Thanks for stoping us before the disaster :) I think all our issues always come down to this weird and inefficient organization we have for docs and common files between

Hi Nicolas, Indeed. But this should be fixed, because we should handle this the same way documentation/releases.html is, with a common one across all releases. With the current implementation, only