<alex.kanavin@...> wrote: this could be an independent layer too.

A question specifically to Denys, how can I actually get this into the mixin repo, and have commit rights to the branch? We've tested this quite well in private, and there are further enhancements

Hello Bruce, I chose the variant based on SRC_URI, but used KERNEL_CONFIG_URI because I got endless recursion between SRC_URI and KERNEL_FEATURES in the kernel recipe I use. I ended up with this

Hi Quentin, Thank you very much for the review. Well, here, the two should go together. I admit my description is probably misleading. My initial "git checkout" was wrong (wrong path), so wasn't

Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage Attendees: Alexandre, Armin, Daiane, Michael, Randy, Richard, Ross, Saul, Stephen, Steve, Tim, Trevor ARs: -

Yes, but this way it 'just works'. I do not think writing complicated instructions in README for what needs to be in local.conf or distro config is a better alternative. Suggestions welcome. Alex

Just out of curiosity: I thought the agreement was that neither PREFERRED_PROVIDER_* nor recipe/provider specific settings should be part of a layer.conf PREFERRED_PROVIDER_go-native as a hard

These recipes are copied verbatim from: https://git.yoctoproject.org/meta-virtualization/tree/?id=dbd37caa6d48772b87426450fb6b816c11acc68a (copy from external source: git:

Reviewed-by: Martin Kaistra <martin.kaistra@...> Signed-off-by: Alexander Kanavin <alex@...> --- COPYING.MIT | 17 +++++++++++++++++ README | 10 ++++++++++

This allows a quick smoke test for whether go toolchain produces working executables. Link:

Link: https://git.yoctoproject.org/poky/tree/meta/recipes-devtools/go?id=20846102156418f187e977ab0bbd557525bbc4e1 (copy from external source: git: https://git.yoctoproject.org/poky/ archive:

This is a verbatim copy of go 1.16 recipes from oe-core master just before they were updated to 1.17. Link:

Reviewed-by: Martin Kaistra <martin.kaistra@...> Signed-off-by: Alexander Kanavin <alex@...> --- COPYING.MIT | 17 +++++++++++++++++ README | 23

<bluelightning@...> wrote: That is good testimony, it will be good to know how this option impacts performance and does it work across architectures and libc's supported in OE.

I guess you can submit a patch, and it can be taken for a spin on the autobuilder? Alex

Another quirk of this - with dunfell, the buildepoxy SDK test fails on Ubuntu 18.04 with -fstack-clash-protection because the version of meson in dunfell uses the same LDFLAGS value for both host

Thanks, Khem. I sent a patch to OE. -- Rudolf J Streif CEO/CTO ibeeto +1.855.442.3386 x700

<rudolf.streif@...> wrote: seems an oversight.

It's been a while, but I was able to build yocto sumo (2.5) using https://github.com/crops/poky-container

Hi all I'd like to install my python3 application in a custom folder with all local packages and data. The source code folder has this