buildroot VS buildroot

I did it few times. It's so much easier nowadays with https://buildroot.org/

If you dig through the rootfs of the K1 it becomes clear that Creality is using buildroot so we should be able to do that ourselves - at least some of us.

An embedded system like Roku doesn't need to "run everything", it just needs to run their "platform", which is probably quite small. It's pretty trivial to assemble your own OS from "off-the-shelf" components. You can use something like buildroot to spin up a new OS in half a day, using only the components you want. You can also use "smaller" components that have far fewer features, meaning less bugs and less updates.

https://github.com/buildroot/buildroot

> I do this for every Windows installation that is used for similar purposes, like embedded machines that has to run a single application, virtual machines, etc.

Have you tried running Linux for these use cases? This sort of thing is an area Linux excels, in my experience.

When you run Windows, you're in for the whole kit and caboodle. Most of the components are proprietary, closed-source black boxes. You can only poke and prod and test and hope things don't break in unexpected ways.

Conversely, Linux can be easy stripped down to a bare bones kernel and a single statically-linked binary. I can run a useful application on top of Linux with the whole system weighing in smaller than bootmgfw.efi.

Something more complex, but still custom, is easily crafted with Buildroot.

https://buildroot.org/

Have a look at the commit history of Linux or buildroot for nice readable commit histories.

Gentoo could teach you more about what is involved in dependency handling and actual ‘construction’ of a Linux system. But Linux From Scratch is a much better teaching tool for learning this, and even things like Buildroot are arguably better than Gentoo for this because they generally force you to care about a lot of the stuff that Gentoo hides away to make the system nicer to use.

Tesla uses Qt and Qt WebEngine uses Chromium, meaning that there is probably in fact a V8 JavaScript engine in any given Tesla.

https://github.com/teslamotors/buildroot/tree/buildroot-2021...

It uses buildroot: - https://github.com/teslamotors/buildroot - https://lists.buildroot.org/pipermail/buildroot/2018-May/221323.html

> Its actually the other way around. Tesla cars are designed more like SpaceX rockets or fighter jets in terms of electronics.

Yeah, the SpaceX and Tesla software stacks for their firmware are similar in a lot of ways, they both heavily use buildroot(https://buildroot.org/) for at least a good bit of their Linux based firmware, good luck getting proper GPL source from them though, Tesla last I checked at least made some effort to publish what appears to be incomplete buildroot source code(https://github.com/teslamotors/buildroot).

SpaceX just inaccurately claims "Because we are not distributing buildroot, we are not legally required to distribute the source code under the GPLv2 license." then ignores you even though they very obviously distribute buildroot based firmware to customers as it's used in the Starlink Dishy antenna(I asked for their buildroot source and have a Dishy antenna, that was their response...and to top it off I'm even a major buildroot contributor). They def have a bunch of cool tech but are super secretive about everything it seems, they don't appear to ever upstream patches or interact with outside software developers.

Uh. There are a lot of things you're getting very wrong here. First, Tesla's OS is absolutely Linux. It may not be running the GNU software stack, but that makes it not a GNU/Linux. Though, I'll point out that it's running the Busybox software stack as well as custom software. Please feel free to review the buildroot build system for Tesla's car OS. https://github.com/teslamotors/buildroot