Yocto, RockPi and SBOMs: Building modern embedded Linux images
1–10 of 125 posts
Re: Yocto, RockPi and SBOMs: Building modern embedded Linux images
#2Love Yocto! It has a learning curve but it took about a week from nothing to an embedded image including Swift and Flutter apps, U-Boot, etc. A curve worth climbing.
Re: Yocto, RockPi and SBOMs: Building modern embedded Linux images
#3Love Yocto! It has a learning curve but it took about a week from nothing to an embedded image including Swift and Flutter apps, U-Boot, etc. A curve worth climbing.
Yeah it definitely isn’t straight forward. But it is complicated for good reasons given how much more complicated stuff it does behind the scenes.
Re: Yocto, RockPi and SBOMs: Building modern embedded Linux images
#4>you can’t run “apt update”
if you want to get a little weird, you can tell yocto to compile everything into deb packages and host them yourself with something like aptly
Re: Yocto, RockPi and SBOMs: Building modern embedded Linux images
#5>you can’t run “apt update” if you want to get a little weird, you can tell yocto to compile everything into deb packages and host them yourself with something like aptly
Yeah that’s true. But if these are embedded devices, you probably want an A/B partition scheme with full transactional updates and rollback.
Re: Yocto, RockPi and SBOMs: Building modern embedded Linux images
#6Love Yocto! It has a learning curve but it took about a week from nothing to an embedded image including Swift and Flutter apps, U-Boot, etc. A curve worth climbing.
I always found buildroot a lot easier to fathom and harness. And certainly flexible enough with the ability patch every included recipe and package.
Re: Yocto, RockPi and SBOMs: Building modern embedded Linux images
#7Love Yocto! It has a learning curve but it took about a week from nothing to an embedded image including Swift and Flutter apps, U-Boot, etc. A curve worth climbing.
A few years ago I had to build a custom embedded image for a high-quality scientific instrument that was going into production, and I made a pass at Yocto - but ultimately decided it wasn't worth the heavy load to get everything in place to do a full build, for the specific SO-DIMM module we were using, so ended up with a custom build script to build the bootable image and all intended embedded applications. This worked out, but I've always been bothered that Yocto didn't pass my first sniff test.
I ended up completing the project on time and under budget by adopting a strict "compiler on-board" approach (i.e. no cross-compiling), so that's where I got a bit dissatisfied with the Yocto approach of having a massive cross-compiling tooling method to deal with.
I'll have to give it another go, but I do find that if I have to have a really beefy machine to get started on an embedded project, somethings' not quite right.
Re: Yocto, RockPi and SBOMs: Building modern embedded Linux images
#8Love Yocto! It has a learning curve but it took about a week from nothing to an embedded image including Swift and Flutter apps, U-Boot, etc. A curve worth climbing.
I always found buildroot a lot easier to fathom and harness. And certainly flexible enough with the ability patch every included recipe and package.
I think it is easier. But for some projects it becomes harder to maintain.
Re: Yocto, RockPi and SBOMs: Building modern embedded Linux images
#9Yocto is pretty great! Unfortunately I feel like it gets a lot of criticism, but usually from people who haven't gotten to learn it. Like "I had to spend 2h on Yocto and this thing suuuuucks, I threw a docker image there and called it a day".
Which is a pity, because when used correctly it's really powerful!
From the article, I can't help but mention that one third of the "key terminology" is about codenames. What do people have with codenames? I can count and easily know that 5 comes after 4. But I don't know how to compare Scarthgap and Dunfell (hell, I can't even remember them).
Re: Yocto, RockPi and SBOMs: Building modern embedded Linux images
#10I read just the title and wondered if this was a yocto post.
I have (accident) become the yocto SME at my $dayjob. Probably the biggest positive has been free SBOM generation, and cooking things like kSLOC counts into recipes.
The learning curve stinks, the build suite is very powerful.