How are you using Yocto with L4Re?
By writing layers and recipes in yocto.
This is the short answer, since yocto is basically independent from Linux.
For a detailed intro see https://bootlin.com/training/yocto/ It can be used to fetch, configure, build, install and boot every part of an embedded system that contains *open source* toolchain, bootloader, kernel, filesystem, startup system, userspace etc.
Unfortunately, this doesn't happen easily and the initial learning curve is steep but a lot of chip manufacturers are moving or have already moved in this direction providing customized yocto bsp layers (for Linux). The kernel is really only (but important) part of the game.
Am Mo., 19. Mai 2025 um 15:13 Uhr schrieb Paul Boddie paul@boddie.org.uk:
On Monday, 19 May 2025 08:11:58 CEST Torsten Wierschin wrote:
Hi there!
In my opinion, the problem discussed here can be solved quite well using yocto or buildroot or something else. If I ever find the time, I'd be happy to publish my yocto build environment for l4re. But maybe someone else will be faster?
How are you using Yocto with L4Re? I'm familiar with tools like Buildroot and derivatives, and it seems plausible that beyond the level of individual packages one could probably replicate the dependency management that the L4Re build system provides.
I have actually used Buildroot with L4Re, but only to generate toolchains with fairly specific requirements, so there was no real integration with L4Re as such.
Paul
P.S. Another question I might ask relates to how you and others are using L4Re, but that deserves a separate thread.