A practical guide to buildroot
4 likes3,051 views
Buildroot is a tool that generates embedded Linux systems by automating the configuration, compilation, and packaging of the system. It produces a root filesystem image ready to deploy on the target architecture. The build process compiles packages and a cross-compilation toolchain, then generates images containing the root filesystem, kernel, and other files needed by the target system. The output of Buildroot is organized into subdirectories containing the built images, toolchain, target and host files, and a staging area simulating the target filesystem.
Ad
More Related Content
What's hot (20)
Viewers also liked (20)
Ad
Similar to A practical guide to buildroot (20)
Ad
More from Emertxe Information Technologies Pvt Ltd (20)
Recently uploaded (20)
A practical guide to buildroot
- 3. Buildroot Quick Start Contents ● Introduction ● Configuration ● Building – Output ● More Infos!!
- 5. Buildroot Introduction ● Buildroot is a set of Makefiles and patches that makes it easy to generate a complete embedded Linux system ● Generates root file system images ready to be used ● Complete build system based on the Linux Kernel configuration system and supports a wide range of target architectures ● It automates the building process of your embedded system and eases the cross-compilation process ● Supports multiple filesystem types for the root filesystem image
- 6. Buildroot Introduction ● Can generate an (e)glibc or uClibc cross-compilation toolchain, or re-use your existing glibc, eglibc or uClibc cross-compilation toolchain ● Supports several hundreds of packages for userspace applications and libraries ● http://buildroot.uclibc.org
- 8. Buildroot Configuration ● Download buildroot package from http://buildroot.uclibc.org ● Untar the package and change directory to buildroot $ tar xvf buildroot-<year>-<month>.tar.bz2 $ cd buildroot-<year>-<month> ● Buildroot supports Linux kernel like configuration options like menuconfig, xconfig etc., ● To configure type $ make menuconfig ● You should get a curses based configurator
- 9. Buildroot Configuration ● Select the target architecture you want to work with ● You may select the toolchain components like – kernel headers – binutils – uclibc – gcc etc., ● You can ignore selecting these components buy selecting the target architecture, but the default selected components would be used while building
- 11. Buildroot Building ● To start the build process just type $ make ● Make sure you don't use make -jN option. Instead you can use BR2_JLEVEL option to run compilation of each individual package with make -jN ● BR2_JLEVEL can be set while configuration at Build options Number of jobs to run simultaneously→
- 12. Buildroot Building ● The make command will generally perform: – Download source files (as required) – Configure, build and install the cross compilation toolchain, or simply import an external toolchain – Configure, build and install selected target packages – Build kernel, bootloader images if selected – Create the root filesystem in selected format ● Buildroot output is stored in a single directory named output/ which will be found in the root directory of buildroot
- 13. Buildroot Building - Output ● The left side shows contents the output directory of the buildroot folder ● This directory contains several subdirectories ● The following slides discuss its contents images build staging buildroot-<YYYY>.<MM> target host output
- 14. Buildroot Building - Output ● All the built images like kernel, bootloader, filesystem are stored here ● These are the files you need to put on the target system images build staging buildroot-<YYYY>.<MM> target host output
- 15. Buildroot Building - Output ● All the components are built here (this includes tools needed by Buildroot on the host and packages compiled for the target) ● Contains one sub directory for each of these components images build staging buildroot-<YYYY>.<MM> target host output
- 16. Buildroot Building - Output ● Contains a hierarchy similar to a root filesystem hierarchy ● Contains the headers and libraries of the cross-compilation toolchain and all the userspace packages selected for the target ● This directory is not intended to be the root filesystem for the target: it contains a lot of development files, unstripped binaries and libraries that make it far too big for an embedded system ● These development files are used to compile libraries and applications for the target that depend on other libraries images build staging buildroot-<YYYY>.<MM> target host output
- 17. Buildroot Building - Output ● Contains almost the complete root filesystem for the target: everything needed is present except the device files in /dev/ and It doesn’t have the correct permissions ● Therefore, this directory should not be used on your target ● Instead, you should use one of the images built in the images/ directory ● If you need an extracted image of the root filesystem for booting over NFS, then use the tarball image generated in images/ and extract it as root ● Contains only the files and libraries needed to run the selected target applications: the development files (headers, etc.) are not present, the binaries are stripped images build staging buildroot-<YYYY>.<MM> target host output
- 18. Buildroot Building - Output ● Contains the installation of tools compiled for the host that are needed for the proper execution of Buildroot, including the cross- compilation toolchain images build staging buildroot-<YYYY>.<MM> target host output
- 20. Thank You