These settings feel distro-specific to me. They're not required for how many of us use the Raspberry Pi so it's best not to force them on everyone. Thanks,

This is something I covered in the Yocto Project Summit in Lyon at the end of October. I'm hoping to get the project documentation updated to reflect what was discussed but that will take a little tim

You could start by looking at how meta-freertos (https://github.com/aehs29/meta-freertos) achieves this. It has support for running the resulting bare-metal app under qemu which you might not need, bu

Hey folks, We had some initial discussion at OEDEM about the patch submission process and how repositories are hosted (see https://docs.google.com/document/d/1Qm1mJ6xLozWW9NgBnokue7TmhwgFP8b2HR8TUlaQw

Do you need this to be an actual package or would you be happy with it just injected into the rootfs via IMAGE_PREPROCESS_COMMAND? If so you could take a look at image-buildinfo.bbclass which seemed t

Hey folks, I'm looking to submit a talk and I'm a little confused on when to register for the YP summit. Should I register now to get the discounted rate or should I wait until the list of accepted sp

Can you just collect the extra packages (ipk/deb/rpm as appropriate), put them in a package feed and install them on-target as required? The package feed doesn't have to be on a webserver, you could p

SRCBRANCH is not a standard variable to my knowledge. You'll probably have to give some more specific info on the recipe that's using it, what bitbake command you ran and the full error message. Thank

This is all covered in the documentation, online tutorials and several excellent books. I'd recommend you set aside some time for learning here as it sounds like you're not familiar with the basic con

In a Yocto Project build, the rootfs is built from packages and the packages are in turn built from recipes. The supported process for adding new software to the image is to write a recipe which creat

You're setting the SRC_URI value only in the do_fetch task. It's needed in at least the do_unpack task as well and possibly other tasks. You could look at setting this in an anonymous python function

Just reading the 2.7 Mega Manual at https://www.yoctoproject.org/docs/2.7/mega-manual/mega-manual.html and noticed a possible bug. "24.15.9. Removed Classes" indicates that the `distrodata` class is n

I'd recommend looking at https://github.com/agherzan/meta-raspberrypi/blob/master/docs/extra-build-config.md to see if there's some extra option you need to enable. If there's nothing documented there

The upstream rpi-4.19.y branch is still unstable and they enjoy rebasing commits. The breaks the commit references used in our recipes. For now I recommend sticking to the 4.14.y kernels for Raspberry

Does your application use setjmp/longjmp or C++ exceptions in the sections built with CGO? I've dug into the runc disassembly as well as adding extra prints and can see that it's at calls to those fun

Hi Lluis, This is an issue I've seen before with runc and gdb. In runc we saw SIGILL which I tracked down to some hideous setjmp/longjmp magic written in C. cgo is used to include this C code in with

Hi Sergio, You could look at how we handle things in the BSP for the Sancloud BeagleBone Enhanced (BBE). This board is based on the BeagleBone Black and so in Yocto Project any overrides, COMPATIBLE_H

There's an excellent "Quick Build" guide in the documentation: https://www.yoctoproject.org/docs/ Beyond that I can highly recommend reading "Embedded Linux Systems with the Yocto Project" by Rudolf S

Hi all, We've got an OpenEmbedded stand again at FOSDEM this year! The event will be held on 2nd & 3rd Feb 2019 at the usual location of ULB Campus du Solbosch in Brussels. I'll be present most of eac

You seem to be a bit confused here by the fact that the poky version number lined up with the year in 2017. See https://wiki.yoctoproject.org/wiki/Releases for some context.