I'm not sure I understand your use case. What kind of information would you want to have in the json file, and why can't it be placed into a separate file next to the .json one? It would help if you p

#bitbake

You need to send your public ssh key to Michael (cc) and explain what access should be granted with that (which repo, which branch(es)). In this case, https://git.yoctoproject.org/meta-lts-mixins/ kir

Can you submit a patch for this please? The mailing list is openembedded-core@. Alex

That may require an unknown amount of fixing in the recipes and classes. Existing code is not designed for co-existing with a different version of itself, and so everything needs to be versioned and c

I think I pushed the work directly to the respecitve branches in meta-lts-mixins. I'd suggest you send the patches here, and we'll sort out the technicalities (I can publish the branch on git.yoctopro

When the slow download is happening, can you please check (e.g. from a process listing), which server specifically is being accessed and with which command? Just to be sure where the problem is. Alex

There is not a lot of interest in maintaining style guides, and associated tooling. My personal feeling is that they don't really help with the truly problematic things in recipes that need a human ey

This is not enough information. To be able to help, I need to see the complete recipe, the command you are issuing, and the complete error message that happens. You can simply publish your work in pub

I think it goes like this. In your recipe you need to install files into the root directory of the partition itself and not its mount point, e.g. strip the mnt/custom prefix. Then you need to create a

Yocto first builds its own toolchain, then uses the toolchain to build the actual software stack for the target. So the host environment can be any Linux distribution. If you can say what the other OS

Please check: https://docs.yoctoproject.org/ref-manual/classes.html#buildstats-bbclass Alex

You need to build the code outside of yocto using the toolchain provided by ubuntu. If built with yocto, your options are to run the tests under qemu usermode, or in full qemu system emulation. Alex

I think you need to inspect the ${WORKDIR} of elfutils-native in detail, particularly the build and install logs in temp/. Does elfutils ./configure get the right options, and does it end up enabling

python-compiler is an obsolete module from python 2.x era and isn't available with 3.x. You can probably remove it from the image altogether: https://python.readthedocs.io/en/v2.7.2/library/compiler.h

Note that the list of supported host distros is set only for the poky reference distro with a weak assignment, and not for oe-core or yocto as a whole. If you do your own tests, and they don't show is

On the other hand, I'm yet to hear an actual case of a broken build due to non-ECC. It's not impossible, but it seems exceedingly rare. You're far more likely to spend 100x as much time on logical err

Note that per its README, meta-virtualization has a dedicated mailing list and an irc channel, so perhaps you could ask there? https://git.yoctoproject.org/meta-virtualization/tree/README says Mailing

There are sample recipes in that layer, e.g. in recipes-demo/images. I suggest you clone it and study that and available image classes. Alex

That layer is not maintained and you should not be using it. If you want to use containers, meta-virtualization is the supported way. Alex

The schedule for upcoming releases is recorded here: https://wiki.yoctoproject.org/wiki/Releases There is no development plan as such (in the sense of a promise to implement new features and timelines