in aid of docs, currently poring over python-based recipes to document how one builds python recipe files, and noticed that numerous recipe files contain an assignment of the form:

<matthias.schoepfer@...> wrote: if it happens on master too then send the patch to openembedded-core mailing list

Hello! I'm totally new to yocto and mainly new to linux development as a whole. Thus, please excuse me if my concerns that I raise here are inadequate. == Context == We are developing a quite simple

Hi Khem! It did help, thank you very much! I needed to repeat this for libgcrypt and libidn2. It does look like a bug though, does it not? Regards,   Matthias

Hello! Ah, just in time to watch live SpaceX's launch: https://blogs.nasa.gov/commercialcrew/ Greetings! Daniel Díaz daniel.diaz@...

I've made a wiki page to track these: https://www.openembedded.org/wiki/Happy_Hours Then next one is scheduled for 2100 UTC on May 27. This is late evening for Europe and morning for New Zealand, so

I created [1] in meta-mortsgna. It is not recommended (bit of a hack / nobody but me and my colleagues use it) but it * works on the fly: Once enabled building the recipe you want to debug is good

The three debugging sections in the yocto manual should help? https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#platdev-gdb-remotedebug Alex

I would think of using IMAGE_GEN_DEBUGFS set to 1 which should generate a debug archive of image see following for detailed

I know I can do $ bitbake base-image -cpopulate_sdk and distribute the resulting SDK to developers (myself included). But suppose I've just built and deployed an image and want to debug a core file

Can you try adding LICENSE_${PN}-lic = "GPL-3.0-with-GCC-exception" in meta/recipes-devtools/gcc/libgcc.inc and see if it helps ?

Hi! I am trying to migrate to dunfell. Out customer does not want GPLv3 or anything like that on the firmware. So - same as in zeus - we have a line: INCOMPATIBLE_LICENSE = "GPLv3 LGPLv3 GPLv3+

Randy Thanks for reviewing it. Hope it will be merged into the main repo soon. Thanks & Regards, Milan Shah MontaVista Software, Bangaluru, India

Hi, I'm trying to figure out how to configure /etc/systemd/coredump.conf in order to get coredump files. I don't appear to have coredumpctl nor can I find a recipe in Yocto or OE Core that looks like

No data, but hunch that a link to the new mail address url is needed...

trying to edit wiki, so trying to create acct at https://wiki.yoctoproject.org/wiki/Special:RequestAccount, and am getting: Error sending mail: Unknown error in PHP's mail() function. are there

i submitted a patch yesterday. rday

Hi, I'm using Warrior - version of Yocto and I have libraries ending up to SDK that are not in image and it's causing problems because applications are trying to look for libraries that are not

OK thanks guys, that's what I though. I did hack 1 since I could, but good to know the hack 2. in case this ever happens for packages I'm not in control of. Cheers, -Damien

Hi Damienm How about using BBMULTICONFIG ? https://www.yoctoproject.org/docs/3.1/mega-manual/mega-manual.html#executing-a-multiple-configuration-build -- Takayasu Ito Technical Expert, Solution