Angstrom ArchLinux Yocto Buildroot: choose OS for embedded x86

I am a little new to the embedded OS, and I want to have a lightweight distribution that will work on the x86 system. Why can I say that Buildroot and ArchLinux are more suitable for x86 targets, while Yocto and Angstrom will be better for a more integrated system like ARM. I did not find any comparison between Buildroot and ArchLinux. I think that perhaps ArchLinux has a better community, while Buildroot is more modular and built-in.

Do you have any tips to give me 4 from above? thanks

+1
source share
3 answers

ArchLinux is just a regular desktop distribution that is distributed through pre-created ISO images. Buildroot and Yocto are tools for building Linux embedded distributions, where you load the build system and then configure it for your purpose (select tool chain, packages, etc.), and then create a bootloader, kernel, and root file system , and Angstrom is a distribution for embedded systems.

Yocto and Angstrom are based on the OpenEmbedded project . Buildroot takes a different approach and uses a Kconfig system such as the Linux kernel.

So far I have only used Buildroot for ARM systems, and I really like this distribution. It is very simple to create and extend your first rootfs. But you may have to try some of these distributions to figure out which one suits your needs. Look at the distribution documentation, tutorials, etc.

If you do not want to compile your rootfs, try ArchLinux . If you are familiar with OpenEmbedded , check out Yocto and Angstrom . If you like Kconfig, try Buildroot .

+4
source

There is also ptxdist , which also has a Kconfig user interface. IMHO has a much smoother learning curve than Yocto.

+1
source

As indicated, ArchLinux is a complete distribution, while Buildroot and Yocto can be used to create highly customizable system images.

Between Yocto and Buildroot, the latter does not have a package manager. Thus, you need to update the full system image if you need to update even one package. However, Yocto needs a much larger installation location on the host computer (rather than the target image) than Buildroot.

0
source

All Articles