Table of Contents
- I. Getting started
- II. User guide
- 6. Buildroot configuration
- 7. Configuration of other components
- 8. General Buildroot usage
- 8.1. make tips
- 8.2. Understanding when a full rebuild is necessary
- 8.3. Understanding how to rebuild packages
- 8.4. Offline builds
- 8.5. Building out-of-tree
- 8.6. Environment variables
- 8.7. Dealing efficiently with filesystem images
- 8.8. Graphing the dependencies between packages
- 8.9. Graphing the build duration
- 8.10. Integration with Eclipse
- 8.11. Advanced usage
- 9. Project-specific customization
- 9.1. Recommended directory structure
- 9.2. Keeping customizations outside of Buildroot
- 9.3. Storing the Buildroot configuration
- 9.4. Storing the configuration of other components
- 9.5. Customizing the generated target filesystem
- 9.6. Adding custom user accounts
- 9.7. Customization after the images have been created
- 9.8. Adding project-specific patches
- 9.9. Adding project-specific packages
- 9.10. Quick guide to storing your project-specific customizations
- 10. Frequently Asked Questions & Troubleshooting
- 10.1. The boot hangs after Starting networkâ¦
- 10.2. Why is there no compiler on the target?
- 10.3. Why are there no development files on the target?
- 10.4. Why is there no documentation on the target?
- 10.5. Why are some packages not visible in the Buildroot config menu?
- 10.6. Why not use the target directory as a chroot directory?
- 10.7. Why doesnât Buildroot generate binary packages (.deb, .ipkgâ¦)?
- 10.8. How to speed-up the build process?
- 11. Known issues
- 12. Legal notice and licensing
- 13. Beyond Buildroot
- III. Developer guide
- 14. How Buildroot works
- 15. Coding style
- 16. Adding support for a particular board
- 17. Adding new packages to Buildroot
- 17.1. Package directory
- 17.2. Config files
- 17.3. The
.mkfile - 17.4. The
.hashfile - 17.5. Infrastructure for packages with specific build systems
- 17.6. Infrastructure for autotools-based packages
- 17.7. Infrastructure for CMake-based packages
- 17.8. Infrastructure for Python packages
- 17.9. Infrastructure for LuaRocks-based packages
- 17.10. Infrastructure for Perl/CPAN packages
- 17.11. Infrastructure for virtual packages
- 17.12. Infrastructure for packages using kconfig for configuration files
- 17.13. Infrastructure for rebar-based packages
- 17.14. Infrastructure for asciidoc documents
- 17.15. Hooks available in the various build steps
- 17.16. Gettext integration and interaction with packages
- 17.17. Tips and tricks
- 17.18. Conclusion
- 18. Patching a package
- 19. Download infrastructure
- 20. Debugging Buildroot
- 21. Contributing to Buildroot
- IV. Appendix
List of Examples
Buildroot 2015.05 manual generated on 2015-05-31 +21:28:39 UTC from git revision 6d73615
The Buildroot manual is written by the Buildroot developers. +It is licensed under the GNU General Public License, version 2. Refer to the +COPYING file in the Buildroot +sources for the full text of this license.
Copyright © 2004-2014 The Buildroot developers
Buildroot is a tool that simplifies and automates the process of +building a complete Linux system for an embedded system, using +cross-compilation.
In order to achieve this, Buildroot is able to generate a +cross-compilation toolchain, a root filesystem, a Linux kernel image +and a bootloader for your target. Buildroot can be used for any +combination of these options, independently (you can for example use +an existing cross-compilation toolchain, and build only your root +filesystem with Buildroot).
Buildroot is useful mainly for people working with embedded systems. +Embedded systems often use processors that are not the regular x86 +processors everyone is used to having in his PC. They can be PowerPC +processors, MIPS processors, ARM processors, etc.
Buildroot supports numerous processors and their variants; it also +comes with default configurations for several boards available +off-the-shelf. Besides this, a number of third-party projects are based on, +or develop their BSP [1] or +SDK [2] on top of Buildroot.
Buildroot is designed to run on Linux systems.
While Buildroot itself will build most host packages it needs for the +compilation, certain standard Linux utilities are expected to be +already installed on the host system. Below you will find an overview of +the mandatory and optional packages (note that package names may vary +between distributions).
+Build tools: +
-
+
which+ -
+
sed+ -
+
make(version 3.81 or any later) + -
+
binutils+ -
+
build-essential(only for Debian based systems) + -
+
gcc(version 2.95 or any later) + -
+
g++(version 2.95 or any later) + -
+
bash+ -
+
patch+ -
+
gzip+ -
+
bzip2+ -
+
perl(version 5.8.7 or any later) + -
+
tar+ -
+
cpio+ -
+
python(version 2.6 or 2.7) + -
+
unzip+ -
+
rsync+
-
+
+Source fetching tools: +
-
+
wget+
-
+
+Configuration interface dependencies: +
For these libraries, you need to install both runtime and development +data, which in many distributions are packaged separately. The +development packages typically have a -dev or -devel suffix.
-
+
ncurses5to use the menuconfig interface + -
+
qt4to use the xconfig interface + -
+
glib2,gtk2andglade2to use the gconfig interface +
-
+
+Source fetching tools: +
In the official tree, most of the package sources are retrieved using +
wgetfrom ftp, http or https locations. A few packages are only +available through a version control system. Moreover, Buildroot is +capable of downloading sources via other tools, likersyncorscp+(refer to Chapter 19, Download infrastructure for more details). If you enable +packages using any of these methods, you will need to install the +corresponding tool on the host system:-
+
bazaar+ -
+
cvs+ -
+
git+ -
+
mercurial+ -
+
rsync+ -
+
scp+ -
+
subversion+
-
+
+Java-related packages, if the Java Classpath needs to be built for + the target system: +
-
+The
javaccompiler + -
+The
jartool +
-
+The
+Documentation generation tools: +
-
+
asciidoc, version 8.6.3 or higher + -
+
w3m+ -
+
pythonwith theargparsemodule (automatically present in 2.7+ and 3.2+) + -
+
dblatex(required for the pdf manual only) +
-
+
+Graph generation tools: +
-
+
graphvizto use graph-depends and <pkg>-graph-depends + -
+
python-matplotlibto use graph-build +
-
+
Buildroot releases are made every 3 months, in February, May, August and +November. Release numbers are in the format YYYY.MM, so for example +2013.02, 2014.08.
Release tarballs are available at http://buildroot.org/downloads/.
If you want to follow development, you can use the daily snapshots or +make a clone of the Git repository. Refer to the +Download page of the Buildroot website +for more details.
Important: you can and should build everything as a normal user. There +is no need to be root to configure and use Buildroot. By running all +commands as a regular user, you protect your system against packages +behaving badly during compilation and installation.
The first step when using Buildroot is to create a configuration. +Buildroot has a nice configuration tool similar to the one you can +find in the Linux kernel or in +BusyBox.
From the buildroot directory, run
$ make menuconfig
for the original curses-based configurator, or
$ make nconfig
for the new curses-based configurator, or
$ make xconfig
for the Qt-based configurator, or
$ make gconfig
for the GTK-based configurator.
All of these "make" commands will need to build a configuration +utility (including the interface), so you may need to install +"development" packages for relevant libraries used by the +configuration utilities. Refer to Chapter 2, System requirements for more details, +specifically the optional requirements +Section 2.2, âOptional packagesâ +to get the dependencies of your favorite interface.
For each menu entry in the configuration tool, you can find associated +help that describes the purpose of the entry. Refer to Chapter 6, Buildroot configuration +for details on some specific configuration aspects.
Once everything is configured, the configuration tool generates a
+.config file that contains the entire configuration. This file will be
+read by the top-level Makefile.
To start the build process, simply run:
$ make
You should never use make -jN with Buildroot: top-level parallel
+make is currently not supported. Instead, use the BR2_JLEVEL option
+to tell Buildroot to run the compilation of each individual package
+with make -jN.
The make command will generally perform the following steps:
- +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 a kernel image, if selected; +
- +build a bootloader image, if selected; +
- +create a root filesystem in selected formats. +
Buildroot output is stored in a single directory, output/.
+This directory contains several subdirectories:
-
+
images/where all the images (kernel image, bootloader and root + filesystem images) are stored. These are the files you need to put + on your target system. + -
+
build/where all the components are built (this includes tools + needed by Buildroot on the host and packages compiled for the + target). This directory contains one subdirectory for each of these + components. + -
+
staging/which contains a hierarchy similar to a root filesystem + hierarchy. This directory contains the headers and libraries of the + cross-compilation toolchain and all the userspace packages selected + for the target. However, 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. + -
+
target/which contains almost the complete root filesystem for + the target: everything needed is present except the device files in +/dev/(Buildroot canât create them because Buildroot doesnât run + as root and doesnât want to run as root). Also, it doesnât have the correct + permissions (e.g. setuid for the busybox binary). Therefore, this directory + should not be used on your target. Instead, you should use one of + the images built in theimages/directory. If you need an + extracted image of the root filesystem for booting over NFS, then + use the tarball image generated inimages/and extract it as + root. Compared tostaging/,target/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. + -
+
host/contains the installation of tools compiled for the host + that are needed for the proper execution of Buildroot, including the + cross-compilation toolchain. +
These commands, make menuconfig|nconfig|gconfig|xconfig and make, are the
+basic ones that allow to easily and quickly generate images fitting
+your needs, with all the features and applications you enabled.
More details about the "make" command usage are given in +Section 8.1, âmake tipsâ.
Like any open source project, Buildroot has different ways to share +information in its community and outside.
Each of those ways may interest you if you are looking for some help, +want to understand Buildroot or contribute to the project.
- +Mailing List +
Buildroot has a mailing list for discussion and development. It is the +main method of interaction for Buildroot users and developers.
Only subscribers to the Buildroot mailing list are allowed to post to +this list. You can subscribe via the +mailing list info +page.
Mails that are sent to the mailing list are also available in the +mailing list archives and +via Gmane, at +
gmane.comp.lib.uclibc.buildroot. +Please search the mailing list archives before asking questions, since +there is a good chance someone else has asked the same question before.- +IRC +
The Buildroot IRC channel #buildroot is +hosted on Freenode. It is a useful place to +ask quick questions or discuss on certain topics.
When asking for help on IRC, share relevant logs or pieces of code +using a code sharing website, such as http://code.bulix.org.
Note that for certain questions, posting to the mailing list may be +better as it will reach more people, both developers and users.
- +Bug tracker +
- Bugs in Buildroot can be reported via the mailing list or alternatively +via the Buildroot +bugtracker. Please refer to Section 21.6, âReporting issues/bugs or getting helpâ before creating a bug +report.
- +Wiki +
- The Buildroot wiki page is hosted on +the eLinux wiki. It contains some useful links, an +overview of past and upcoming events, and a TODO list.
- +Patchwork +
Patchwork is a web-based patch tracking system designed to facilitate +the contribution and management of contributions to an open-source +project. Patches that have been sent to a mailing list are 'caught' by +the system, and appear on a web page. Any comments posted that +reference the patch are appended to the patch page too. For more +information on Patchwork see +http://jk.ozlabs.org/projects/patchwork/.
Buildrootâs Patchwork website is mainly for use by Buildrootâs +maintainer to ensure patches arenât missed. It is also used by Buildroot +patch reviewers (see also Section 21.3.1, âApplying Patches from Patchworkâ). +However, since the website exposes patches and their corresponding +review comments in a clean and concise web interface, it can be useful +for all Buildroot developers.
The Buildroot patch management interface is available at +http://patchwork.buildroot.org.
All the configuration options in make *config have a help text
+providing details about the option.
The make *config commands also offer a search tool. Read the help
+message in the different frontend menus to know how to use it:
-
+in menuconfig, the search tool is called by pressing
/; + -
+in xconfig, the search tool is called by pressing
Ctrl+f. +
The result of the search shows the help message of the matching items. +In menuconfig, numbers in the left column provide a shortcut to the +corresponding entry. Just type this number to directly jump to the +entry, or to the containing menu in case the entry is not selectable due +to a missing dependency.
Although the menu structure and the help text of the entries should be +sufficiently self-explanatory, a number of topics require additional +explanation that cannot easily be covered in the help text and are +therefore covered in the following sections.
A compilation toolchain is the set of tools that allows you to compile
+code for your system. It consists of a compiler (in our case, gcc),
+binary utils like assembler and linker (in our case, binutils) and a
+C standard library (for example
+GNU Libc,
+uClibc).
The system installed on your development station certainly already has +a compilation toolchain that you can use to compile an application +that runs on your system. If youâre using a PC, your compilation +toolchain runs on an x86 processor and generates code for an x86 +processor. Under most Linux systems, the compilation toolchain uses +the GNU libc (glibc) as the C standard library. This compilation +toolchain is called the "host compilation toolchain". The machine on +which it is running, and on which youâre working, is called the "host +system" [3].
The compilation toolchain is provided by your distribution, and +Buildroot has nothing to do with it (other than using it to build a +cross-compilation toolchain and other tools that are run on the +development host).
As said above, the compilation toolchain that comes with your system +runs on and generates code for the processor in your host system. As +your embedded system has a different processor, you need a +cross-compilation toolchain - a compilation toolchain that runs on +your host system but generates code for your target system (and +target processor). For example, if your host system uses x86 and your +target system uses ARM, the regular compilation toolchain on your host +runs on x86 and generates code for x86, while the cross-compilation +toolchain runs on x86 and generates code for ARM.
Buildroot provides two solutions for the cross-compilation toolchain:
-
+The internal toolchain backend, called
Buildroot toolchainin + the configuration interface. + -
+The external toolchain backend, called
External toolchainin + the configuration interface. +
The choice between these two solutions is done using the Toolchain
+Type option in the Toolchain menu. Once one solution has been
+chosen, a number of configuration options appear, they are detailed in
+the following sections.
The internal toolchain backend is the backend where Buildroot builds +by itself a cross-compilation toolchain, before building the userspace +applications and libraries for your target embedded system.
This backend supports several C libraries: +uClibc, the +glibc and +eglibc.
Once you have selected this backend, a number of options appear. The +most important ones allow to:
-
+Change the version of the Linux kernel headers used to build the
+ toolchain. This item deserves a few explanations. In the process of
+ building a cross-compilation toolchain, the C library is being
+ built. This library provides the interface between userspace
+ applications and the Linux kernel. In order to know how to "talk"
+ to the Linux kernel, the C library needs to have access to the
+ Linux kernel headers (i.e. the
.hfiles from the kernel), which + define the interface between userspace and the kernel (system + calls, data structures, etc.). Since this interface is backward + compatible, the version of the Linux kernel headers used to build + your toolchain do not need to match exactly the version of the + Linux kernel you intend to run on your embedded system. They only + need to have a version equal or older to the version of the Linux + kernel you intend to run. If you use kernel headers that are more + recent than the Linux kernel you run on your embedded system, then + the C library might be using interfaces that are not provided by + your Linux kernel. + - +Change the version of the GCC compiler, binutils and the C library. +
-
+Select a number of toolchain options (uClibc only): whether the
+ toolchain should have RPC support (used mainly for NFS),
+ wide-char support, locale support (for internationalization),
+ C++ support or thread support. Depending on which options you choose,
+ the number of userspace applications and libraries visible in
+ Buildroot menus will change: many applications and libraries require
+ certain toolchain options to be enabled. Most packages show a comment
+ when a certain toolchain option is required to be able to enable
+ those packages. If needed, you can further refine the uClibc
+ configuration by running
make uclibc-menuconfig. Note however that + all packages in Buildroot are tested against the default uClibc + configuration bundled in Buildroot: if you deviate from this + configuration by removing features from uClibc, some packages may no + longer build. +
It is worth noting that whenever one of those options is modified, +then the entire toolchain and system must be rebuilt. See +Section 8.2, âUnderstanding when a full rebuild is necessaryâ.
Advantages of this backend:
- +Well integrated with Buildroot +
- +Fast, only builds whatâs necessary +
Drawbacks of this backend:
-
+Rebuilding the toolchain is needed when doing
make clean, which + takes time. If youâre trying to reduce your build time, consider + using the External toolchain backend. +
The external toolchain backend allows to use existing pre-built +cross-compilation toolchains. Buildroot knows about a number of +well-known cross-compilation toolchains (from +Linaro for ARM, +Sourcery +CodeBench for ARM, x86, x86-64, PowerPC, MIPS and SuperH, +Blackfin toolchains +from Analog Devices, etc.) and is capable of downloading them +automatically, or it can be pointed to a custom toolchain, either +available for download or installed locally.
Then, you have three solutions to use an external toolchain:
-
+Use a predefined external toolchain profile, and let Buildroot
+ download, extract and install the toolchain. Buildroot already knows
+ about a few CodeSourcery, Linaro, Blackfin and Xilinx toolchains.
+ Just select the toolchain profile in
Toolchainfrom the + available ones. This is definitely the easiest solution. + -
+Use a predefined external toolchain profile, but instead of having
+ Buildroot download and extract the toolchain, you can tell Buildroot
+ where your toolchain is already installed on your system. Just
+ select the toolchain profile in
Toolchainthrough the available + ones, unselectDownload toolchain automatically, and fill the +Toolchain pathtext entry with the path to your cross-compiling + toolchain. + -
+Use a completely custom external toolchain. This is particularly
+ useful for toolchains generated using crosstool-NG or with Buildroot
+ itself. To do this, select the
Custom toolchainsolution in the +Toolchainlist. You need to fill theToolchain path,Toolchain + prefixandExternal toolchain C libraryoptions. Then, you have + to tell Buildroot what your external toolchain supports. If your + external toolchain uses the glibc library, you only have to tell + whether your toolchain supports C++ or not and whether it has + built-in RPC support. If your external toolchain uses the uClibc + library, then you have to tell Buildroot if it supports RPC, + wide-char, locale, program invocation, threads and C++. + At the beginning of the execution, Buildroot will tell you if + the selected options do not match the toolchain configuration. +
Our external toolchain support has been tested with toolchains from +CodeSourcery and Linaro, toolchains generated by +crosstool-NG, and toolchains generated by +Buildroot itself. In general, all toolchains that support the +sysroot feature should work. If not, do not hesitate to contact the +developers.
We do not support toolchains or SDK generated by OpenEmbedded or +Yocto, because these toolchains are not pure toolchains (i.e. just the +compiler, binutils, the C and C++ libraries). Instead these toolchains +come with a very large set of pre-compiled libraries and +programs. Therefore, Buildroot cannot import the sysroot of the +toolchain, as it would contain hundreds of megabytes of pre-compiled +libraries that are normally built by Buildroot.
We also do not support using the distribution toolchain (i.e. the +gcc/binutils/C library installed by your distribution) as the +toolchain to build software for the target. This is because your +distribution toolchain is not a "pure" toolchain (i.e. only with the +C/C++ library), so we cannot import it properly into the Buildroot +build environment. So even if you are building a system for a x86 or +x86_64 target, you have to generate a cross-compilation toolchain with +Buildroot or crosstool-NG.
If you want to generate a custom toolchain for your project, that can +be used as an external toolchain in Buildroot, our recommendation is +definitely to build it with crosstool-NG. We +recommend to build the toolchain separately from Buildroot, and then +import it in Buildroot using the external toolchain backend.
Advantages of this backend:
- +Allows to use well-known and well-tested cross-compilation + toolchains. +
- +Avoids the build time of the cross-compilation toolchain, which is + often very significant in the overall build time of an embedded + Linux system. +
- +Not limited to uClibc: glibc and eglibc toolchains are supported. +
Drawbacks of this backend:
- +If your pre-built external toolchain has a bug, may be hard to get a + fix from the toolchain vendor, unless you build your external + toolchain by yourself using Crosstool-NG. +
When using an external toolchain, Buildroot generates a wrapper program,
+that transparently passes the appropriate options (according to the
+configuration) to the external toolchain programs. In case you need to
+debug this wrapper to check exactly what arguments are passed, you can
+set the environment variable BR2_DEBUG_WRAPPER to either one of:
-
+
0, empty or not set: no debug + -
+
1: trace all arguments on a single line + -
+
2: trace one argument per line +
On a Linux system, the /dev directory contains special files, called
+device files, that allow userspace applications to access the
+hardware devices managed by the Linux kernel. Without these device
+files, your userspace applications would not be able to use the
+hardware devices, even if they are properly recognized by the Linux
+kernel.
Under System configuration, /dev management, Buildroot offers four
+different solutions to handle the /dev directory :
-
+The first solution is Static using device table. This is the old
+ classical way of handling device files in Linux. With this method,
+ the device files are persistently stored in the root filesystem
+ (i.e. they persist across reboots), and there is nothing that will
+ automatically create and remove those device files when hardware
+ devices are added or removed from the system. Buildroot therefore
+ creates a standard set of device files using a device table, the
+ default one being stored in
system/device_table_dev.txtin the + Buildroot source code. This file is processed when Buildroot + generates the final root filesystem image, and the device files + are therefore not visible in theoutput/targetdirectory. The +BR2_ROOTFS_STATIC_DEVICE_TABLEoption allows to change the + default device table used by Buildroot, or to add an additional + device table, so that additional device files are created by + Buildroot during the build. So, if you use this method, and a + device file is missing in your system, you can for example create + aboard/<yourcompany>/<yourproject>/device_table_dev.txtfile + that contains the description of your additional device files, + and then you can setBR2_ROOTFS_STATIC_DEVICE_TABLEto +system/device_table_dev.txt + board/<yourcompany>/<yourproject>/device_table_dev.txt. For more + details about the format of the device table file, see + Chapter 22, Makedev syntax documentation. + -
+The second solution is Dynamic using devtmpfs only. devtmpfs is
+ a virtual filesystem inside the Linux kernel that has been
+ introduced in kernel 2.6.32 (if you use an older kernel, it is not
+ possible to use this option). When mounted in
/dev, this virtual + filesystem will automatically make device files appear and + disappear as hardware devices are added and removed from the + system. This filesystem is not persistent across reboots: it is + filled dynamically by the kernel. Using devtmpfs requires the + following kernel configuration options to be enabled: +CONFIG_DEVTMPFSandCONFIG_DEVTMPFS_MOUNT. When Buildroot is in + charge of building the Linux kernel for your embedded device, it + makes sure that those two options are enabled. However, if you + build your Linux kernel outside of Buildroot, then it is your + responsibility to enable those two options (if you fail to do so, + your Buildroot system will not boot). + -
+The third solution is Dynamic using mdev. This method also relies
+ on the devtmpfs virtual filesystem detailed above (so the
+ requirement to have
CONFIG_DEVTMPFSandCONFIG_DEVTMPFS_MOUNT+ enabled in the kernel configuration still apply), but adds the +mdevuserspace utility on top of it.mdevis a program part of + BusyBox that the kernel will call every time a device is added or + removed. Thanks to the/etc/mdev.confconfiguration file,mdev+ can be configured to for example, set specific permissions or + ownership on a device file, call a script or application whenever a + device appears or disappear, etc. Basically, it allows userspace + to react on device addition and removal events.mdevcan for + example be used to automatically load kernel modules when devices + appear on the system.mdevis also important if you have devices + that require a firmware, as it will be responsible for pushing the + firmware contents to the kernel.mdevis a lightweight + implementation (with fewer features) ofudev. For more details + aboutmdevand the syntax of its configuration file, see + http://git.busybox.net/busybox/tree/docs/mdev.txt. + -
+The fourth solution is Dynamic using eudev. This method also
+ relies on the devtmpfs virtual filesystem detailed above, but
+ adds the
eudevuserspace daemon on top of it.eudevis a daemon + that runs in the background, and gets called by the kernel when a + device gets added or removed from the system. It is a more + heavyweight solution thanmdev, but provides higher flexibility. +eudevis a standalone version ofudev, the original userspace + daemon used in most desktop Linux distributions, which is now part + of Systemd. For more details, see http://en.wikipedia.org/wiki/Udev. +
The Buildroot developers recommendation is to start with the Dynamic +using devtmpfs only solution, until you have the need for userspace +to be notified when devices are added/removed, or if firmwares are +needed, in which case Dynamic using mdev is usually a good solution.
Note that if systemd is chosen as init system, /dev management will
+be performed by the udev program provided by systemd.
The init program is the first userspace program started by the +kernel (it carries the PID number 1), and is responsible for starting +the userspace services and programs (for example: web server, +graphical applications, other network servers, etc.).
Buildroot allows to use three different types of init systems, which
+can be chosen from System configuration, Init system:
-
+The first solution is BusyBox. Amongst many programs, BusyBox has
+ an implementation of a basic
initprogram, which is sufficient + for most embedded systems. Enabling theBR2_INIT_BUSYBOXwill + ensure BusyBox will build and install itsinitprogram. This is + the default solution in Buildroot. The BusyBoxinitprogram will + read the/etc/inittabfile at boot to know what to do. The syntax + of this file can be found in + http://git.busybox.net/busybox/tree/examples/inittab (note that + BusyBoxinittabsyntax is special: do not use a randominittab+ documentation from the Internet to learn about BusyBox +inittab). The defaultinittabin Buildroot is stored in +system/skeleton/etc/inittab. Apart from mounting a few important + filesystems, the main job the default inittab does is to start the +/etc/init.d/rcSshell script, and start agettyprogram (which + provides a login prompt). + -
+The second solution is systemV. This solution uses the old
+ traditional sysvinit program, packed in Buildroot in
+
package/sysvinit. This was the solution used in most desktop + Linux distributions, until they switched to more recent + alternatives such as Upstart or Systemd.sysvinitalso works with + aninittabfile (which has a slightly different syntax than the + one from BusyBox). The defaultinittabinstalled with this init + solution is located inpackage/sysvinit/inittab. + -
+The third solution is systemd.
systemdis the new generation + init system for Linux. It does far more than traditional init + programs: aggressive parallelization capabilities, uses socket and + D-Bus activation for starting services, offers on-demand starting + of daemons, keeps track of processes using Linux control groups, + supports snapshotting and restoring of the system state, + etc.systemdwill be useful on relatively complex embedded + systems, for example the ones requiring D-Bus and services + communicating between each other. It is worth noting thatsystemd+ brings a fairly big number of large dependencies:dbus,udev+ and more. For more details aboutsystemd, see + http://www.freedesktop.org/wiki/Software/systemd. +
The solution recommended by Buildroot developers is to use the +BusyBox init as it is sufficient for most embedded +systems. systemd can be used for more complex situations.
[3] This terminology differs from what is used by GNU +configure, where the host is the machine on which the application will +run (which is usually the same as target)
Before attempting to modify any of the components below, make sure you +have already configured Buildroot itself, and have enabled the +corresponding package.
- +BusyBox +
If you already have a BusyBox configuration file, you can directly +specify this file in the Buildroot configuration, using +
BR2_PACKAGE_BUSYBOX_CONFIG. Otherwise, Buildroot will start from a +default BusyBox configuration file.To make subsequent changes to the configuration, use
make +busybox-menuconfigto open the BusyBox configuration editor.It is also possible to specify a BusyBox configuration file through an +environment variable, although this is not recommended. Refer to +Section 8.6, âEnvironment variablesâ for more details.
- +uClibc +
- Configuration of uClibc is done in the same way as for BusyBox. The
+configuration variable to specify an existing configuration file is
+
BR2_UCLIBC_CONFIG. The command to make subsequent changes ismake +uclibc-menuconfig. - +Linux kernel +
If you already have a kernel configuration file, you can directly +specify this file in the Buildroot configuration, using +
BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG.If you do not yet have a kernel configuration file, you can either start +by specifying a defconfig in the Buildroot configuration, using +
BR2_LINUX_KERNEL_USE_DEFCONFIG, or start by creating an empty file and +specifying it as custom configuration file, using +BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG.To make subsequent changes to the configuration, use
make +linux-menuconfigto open the Linux configuration editor.- +Barebox +
- Configuration of Barebox is done in the same way as for the Linux
+kernel. The corresponding configuration variables are
+
BR2_TARGET_BAREBOX_USE_CUSTOM_CONFIGand +BR2_TARGET_BAREBOX_USE_DEFCONFIG. To open the configuration editor, +usemake barebox-menuconfig.
This is a collection of tips that help you make the most of Buildroot.
Display all commands executed by make:Â +
$ make V=1 <target>
+
Display the list of boards with a defconfig:Â +
$ make list-defconfigs
+
Display all available targets:Â +
$ make help
+
Not all targets are always available,
+some settings in the .config file may hide some targets:
-
+
busybox-menuconfigonly works whenbusyboxis enabled; + -
+
linux-menuconfigandlinux-savedefconfigonly work when +linuxis enabled; + -
+
uclibc-menuconfigis only available when the uClibc C library is + selected in the internal toolchain backend; + -
+
barebox-menuconfigandbarebox-savedefconfigonly work when the +bareboxbootloader is enabled. +
Cleaning:Â Explicit cleaning is required when any of the architecture or toolchain +configuration options are changed.
To delete all build products (including build directories, host, staging +and target trees, the images and the toolchain):
$ make clean
Generating the manual:Â The present manual sources are located in the docs/manual directory. +To generate the manual:
$ make manual-clean + $ make manual
The manual outputs will be generated in output/docs/manual.
Notes
- +A few tools are required to build the documentation (see: + Section 2.2, âOptional packagesâ). +
Resetting Buildroot for a new target:Â To delete all build products as well as the configuration:
$ make distclean
Notes. If ccache is enabled, running make clean or distclean does
+not empty the compiler cache used by Buildroot. To delete it, refer
+to Section 8.11.3, âUsing ccache in Buildrootâ.
Buildroot does not attempt to detect what parts of the system should
+be rebuilt when the system configuration is changed through make
+menuconfig, make xconfig or one of the other configuration
+tools. In some cases, Buildroot should rebuild the entire system, in
+some cases, only a specific subset of packages. But detecting this in
+a completely reliable manner is very difficult, and therefore the
+Buildroot developers have decided to simply not attempt to do this.
Instead, it is the responsibility of the user to know when a full +rebuild is necessary. As a hint, here are a few rules of thumb that +can help you understand how to work with Buildroot:
- +When the target architecture configuration is changed, a complete + rebuild is needed. Changing the architecture variant, the binary + format or the floating point strategy for example has an impact on + the entire system. +
- +When the toolchain configuration is changed, a complete rebuild + generally is needed. Changing the toolchain configuration often + involves changing the compiler version, the type of C library or + its configuration, or some other fundamental configuration item, + and these changes have an impact on the entire system. +
-
+When an additional package is added to the configuration, a full
+ rebuild is not necessarily needed. Buildroot will detect that this
+ package has never been built, and will build it. However, if this
+ package is a library that can optionally be used by packages that
+ have already been built, Buildroot will not automatically rebuild
+ those. Either you know which packages should be rebuilt, and you
+ can rebuild them manually, or you should do a full rebuild. For
+ example, letâs suppose you have built a system with the
ctorrent+ package, but withoutopenssl. Your system works, but you realize + you would like to have SSL support inctorrent, so you enable the +opensslpackage in Buildroot configuration and restart the + build. Buildroot will detect thatopensslshould be built and + will be build it, but it will not detect thatctorrentshould be + rebuilt to benefit fromopensslto add OpenSSL support. You will + either have to do a full rebuild, or rebuildctorrentitself. + - +When a package is removed from the configuration, Buildroot does + not do anything special. It does not remove the files installed by + this package from the target root filesystem or from the toolchain + sysroot. A full rebuild is needed to get rid of this + package. However, generally you donât necessarily need this package + to be removed right now: you can wait for the next lunch break to + restart the build from scratch. +
- +When the sub-options of a package are changed, the package is not + automatically rebuilt. After making such changes, rebuilding only + this package is often sufficient, unless enabling the package + sub-option adds some features to the package that are useful for + another package which has already been built. Again, Buildroot does + not track when a package should be rebuilt: once a package has been + built, it is never rebuilt unless explicitly told to do so. +
-
+When a change to the root filesystem skeleton is made, a full
+ rebuild is needed. However, when changes to the root filesystem
+ overlay, a post-build script or a post-image script are made,
+ there is no need for a full rebuild: a simple
makeinvocation + will take the changes into account. +
Generally speaking, when youâre facing a build error and youâre unsure +of the potential consequences of the configuration changes youâve +made, do a full rebuild. If you get the same build error, then you are +sure that the error is not related to partial rebuilds of packages, +and if this error occurs with packages from the official Buildroot, do +not hesitate to report the problem! As your experience with Buildroot +progresses, you will progressively learn when a full rebuild is really +necessary, and you will save more and more time.
For reference, a full rebuild is achieved by running:
$ make clean all
One of the most common questions asked by Buildroot users is how to +rebuild a given package or how to remove a package without rebuilding +everything from scratch.
Removing a package is unsupported by Buildroot without
+rebuilding from scratch. This is because Buildroot doesnât keep track
+of which package installs what files in the output/staging and
+output/target directories, or which package would be compiled differently
+depending on the availability of another package.
The easiest way to rebuild a single package from scratch is to remove
+its build directory in output/build. Buildroot will then re-extract,
+re-configure, re-compile and re-install this package from scratch. You
+can ask buildroot to do this with the make <package>-dirclean command.
On the other hand, if you only want to restart the build process of a
+package from its compilation step, you can run make
+<package>-rebuild, followed by make or make <package>. It will
+restart the compilation and installation of the package, but not from
+scratch: it basically re-executes make and make install
+inside the package, so it will only rebuild files that changed.
If you want to restart the build process of a package from its
+configuration step, you can run make <package>-reconfigure, followed
+by make or make <package>. It will restart the configuration,
+compilation and installation of the package.
Internally, Buildroot creates so-called stamp files to keep track of
+which build steps have been completed for each package. They are
+stored in the package build directory,
+output/build/<package>-<version>/ and are named
+.stamp_<step-name>. The commands detailed above simply manipulate
+these stamp files to force Buildroot to restart a specific set of
+steps of a package build process.
Further details about package special make targets are explained in +Section 8.11.5, âPackage-specific make targetsâ.
If you intend to do an offline build and just want to download +all sources that you previously selected in the configurator +(menuconfig, nconfig, xconfig or gconfig), then issue:
$ make source
You can now disconnect or copy the content of your dl
+directory to the build-host.
As default, everything built by Buildroot is stored in the directory
+output in the Buildroot tree.
Buildroot also supports building out of tree with a syntax similar to
+the Linux kernel. To use it, add O=<directory> to the make command
+line:
$ make O=/tmp/build
Or:
$ cd /tmp/build; make O=$PWD -C path/to/buildroot
All the output files will be located under /tmp/build. If the O
+path does not exist, Buildroot will create it.
Note: the O path can be either an absolute or a relative path, but if itâs
+passed as a relative path, it is important to note that it is interpreted
+relative to the main Buildroot source directory, not the current working
+directory.
When using out-of-tree builds, the Buildroot .config and temporary
+files are also stored in the output directory. This means that you can
+safely run multiple builds in parallel using the same source tree as
+long as they use unique output directories.
For ease of use, Buildroot generates a Makefile wrapper in the output
+directory - so after the first run, you no longer need to pass O=<â¦>
+and -C <â¦>, simply run (in the output directory):
$ make <target>
Buildroot also honors some environment variables, when they are passed
+to make or set in the environment:
-
+
HOSTCXX, the host C++ compiler to use + -
+
HOSTCC, the host C compiler to use + -
+
UCLIBC_CONFIG_FILE=<path/to/.config>, path to + the uClibc configuration file, used to compile uClibc, if an + internal toolchain is being built. + + Note that the uClibc configuration file can also be set from the + configuration interface, so through the Buildroot.configfile; this + is the recommended way of setting it. + + -
+
BUSYBOX_CONFIG_FILE=<path/to/.config>, path to + the BusyBox configuration file. + + Note that the BusyBox configuration file can also be set from the + configuration interface, so through the Buildroot.configfile; this + is the recommended way of setting it. + + -
+
BR2_DL_DIRto override the directory in which + Buildroot stores/retrieves downloaded files + + Note that the Buildroot download directory can also be set from the + configuration interface, so through the Buildroot.configfile; this + is the recommended way of setting it. + -
+
BR2_GRAPH_ALT, if set and non-empty, to use an alternate color-scheme in + build-time graphs + -
+
BR2_GRAPH_OUTto set the filetype of generated graphs, eitherpdf(the + default), orpng. + -
+
BR2_GRAPH_DEPS_OPTSto pass extra options to the dependency graph; see + Section 8.8, âGraphing the dependencies between packagesâ for the accepted options + -
+
BR2_GRAPH_DOT_OPTSis passed verbatim as options to thedotutility to + draw the dependency graph. +
An example that uses config files located in the toplevel directory and +in your $HOME:
$ make UCLIBC_CONFIG_FILE=uClibc.config BUSYBOX_CONFIG_FILE=$HOME/bb.config
If you want to use a compiler other than the default gcc
+or g++ for building helper-binaries on your host, then do
$ make HOSTCXX=g++-4.3-HEAD HOSTCC=gcc-4.3-HEAD
Filesystem images can get pretty big, depending on the filesystem you choose, +the number of packages, whether you provisioned free space⦠Yet, some +locations in the filesystems images may just be empty (e.g. a long run of +zeroes); such a file is called a sparse file.
Most tools can handle sparse files efficiently, and will only store or write +those parts of a sparse file that are not empty.
For example:
+
taraccepts the-Soption to tell it to only store non-zero blocks + of sparse files: +-
+
tar cf archive.tar -S [filesâ¦]will efficiently store sparse files + in a tarball + -
+
tar xf archive.tar -Swill efficiently store sparse files extracted + from a tarball +
-
+
+
cpaccepts the--sparse=WHENoption (WHENis one ofauto, +neveroralways): +-
+
cp --sparse=always source.file dest.filewill makedest.filea + sparse file ifsource.filehas long runs of zeroes +
-
+
Other tools may have similar options. Please consult their respective man +pages.
You can use sparse files if you need to store the filesystem images (e.g. +to transfer from one machine to another), or if you need to send them (e.g. +to the Q&A team).
Note however that flashing a filesystem image to a device while using the
+sparse mode of dd may result in a broken filesystem (e.g. the block bitmap
+of an ext2 filesystem may be corrupted; or, if you have sparse files in
+your filesystem, those parts may not be all-zeroes when read back). You
+should only use sparse files when handling files on the build machine, not
+when transferring them to an actual device that will be used on the target.
One of Buildrootâs jobs is to know the dependencies between packages, +and make sure they are built in the right order. These dependencies +can sometimes be quite complicated, and for a given system, it is +often not easy to understand why such or such package was brought into +the build by Buildroot.
In order to help understanding the dependencies, and therefore better +understand what is the role of the different components in your +embedded Linux system, Buildroot is capable of generating dependency +graphs.
To generate a dependency graph of the full system you have compiled, +simply run:
make graph-depends
You will find the generated graph in
+output/graphs/graph-depends.pdf.
If your system is quite large, the dependency graph may be too complex +and difficult to read. It is therefore possible to generate the +dependency graph just for a given package:
make <pkg>-graph-depends
You will find the generated graph in
+output/graph/<pkg>-graph-depends.pdf.
Note that the dependency graphs are generated using the dot tool
+from the Graphviz project, which you must have installed on your
+system to use this feature. In most distributions, it is available as
+the graphviz package.
By default, the dependency graphs are generated in the PDF
+format. However, by passing the BR2_GRAPH_OUT environment variable, you
+can switch to other output formats, such as PNG, PostScript or
+SVG. All formats supported by the -T option of the dot tool are
+supported.
BR2_GRAPH_OUT=svg make graph-depends
The graph-depends behaviour can be controlled by setting options in the
+BR2_GRAPH_DEPS_OPTS environment variable. The accepted options are:
-
+
--depth N,-d N, to limit the dependency depth toNlevels. The + default,0, means no limit. + -
+
--stop-on PKG,-s PKG, to stop the graph on the packagePKG. +PKGcan be an actual package name, a glob, or the keyword virtual + (to stop on virtual packages). The package is still present on the + graph, but its dependencies are not. + -
+
--exclude PKG,-x PKG, like--stop-on, but also omitsPKGfrom + the graph. + -
+
--transitive,--no-transitive, to draw (or not) the transitive + dependencies. The default is to not draw transitive dependencies. + -
+
--colours R,T,H, the comma-separated list of colours to draw the + root package (R), the target packages (T) and the host packages + (H). Defaults to:lightblue,grey,gainsboro+
BR2_GRAPH_DEPS_OPTS='-d 3 --no-transitive --colours=red,green,blue' make graph-depends
When the build of a system takes a long time, it is sometimes useful +to be able to understand which packages are the longest to build, to +see if anything can be done to speed up the build. In order to help +such build time analysis, Buildroot collects the build time of each +step of each package, and allows to generate graphs from this data.
To generate the build time graph after a build, run:
make graph-build
This will generate a set of files in output/graphs :
-
+
build.hist-build.pdf, a histogram of the build time for each + package, ordered in the build order. + -
+
build.hist-duration.pdf, a histogram of the build time for each + package, ordered by duration (longest first) + -
+
build.hist-name.pdf, a histogram of the build time for each + package, order by package name. + -
+
build.pie-packages.pdf, a pie chart of the build time per package + -
+
build.pie-steps.pdf, a pie chart of the global time spent in each + step of the packages build process. +
This graph-build target requires the Python Matplotlib and Numpy
+libraries to be installed (python-matplotlib and python-numpy on
+most distributions), and also the argparse module if youâre using a
+Python version older than 2.7 (python-argparse on most
+distributions).
By default, the output format for the graph is PDF, but a different
+format can be selected using the BR2_GRAPH_OUT environment variable. The
+only other format supported is PNG:
BR2_GRAPH_OUT=png make graph-build
While a part of the embedded Linux developers like classical text +editors like Vim or Emacs, and command-line based interfaces, a number +of other embedded Linux developers like richer graphical interfaces to +do their development work. Eclipse being one of the most popular +Integrated Development Environment, Buildroot integrates with Eclipse +in order to ease the development work of Eclipse users.
Our integration with Eclipse simplifies the compilation, remote +execution and remote debugging of applications and libraries that are +built on top of a Buildroot system. It does not integrate the +Buildroot configuration and build processes themselves with +Eclipse. Therefore, the typical usage model of our Eclipse integration +would be:
-
+Configure your Buildroot system with
make menuconfig,make + xconfigor any other configuration interface provided with + Buildroot. + -
+Build your Buildroot system by running
make. + - +Start Eclipse to develop, execute and debug your own custom + applications and libraries, that will rely on the libraries built + and installed by Buildroot. +
The Buildroot Eclipse integration installation process and usage is +described in detail at +https://github.com/mbats/eclipse-buildroot-bundle/wiki.
You may want to compile, for your target, your own programs or other +software that are not packaged in Buildroot. In order to do this you +can use the toolchain that was generated by Buildroot.
The toolchain generated by Buildroot is located by default in
+output/host/. The simplest way to use it is to add
+output/host/usr/bin/ to your PATH environment variable and then to
+use ARCH-linux-gcc, ARCH-linux-objdump, ARCH-linux-ld, etc.
It is possible to relocate the toolchain - but then --sysroot must
+be passed every time the compiler is called to tell where the
+libraries and header files are.
It is also possible to generate the Buildroot toolchain in a directory
+other than output/host by using the Build options â Host dir
+option. This could be useful if the toolchain must be shared with
+other users.
Buildroot allows to do cross-debugging, where the debugger runs on the
+build machine and communicates with gdbserver on the target to
+control the execution of the program.
To achieve this:
-
+If you are using an internal toolchain (built by Buildroot), you
+ must enable
BR2_PACKAGE_HOST_GDB,BR2_PACKAGE_GDBand +BR2_PACKAGE_GDB_SERVER. This ensures that both the cross gdb and + gdbserver get built, and that gdbserver gets installed to your target. + -
+If you are using an external toolchain, you should enable
+
BR2_TOOLCHAIN_EXTERNAL_GDB_SERVER_COPY, which will copy the + gdbserver included with the external toolchain to the target. If your + external toolchain does not have a cross gdb or gdbserver, it is also + possible to let Buildroot build them, by enabling the same options as + for the internal toolchain backend. +
Now, to start debugging a program called foo, you should run on the
+target:
gdbserver :2345 foo
This will cause gdbserver to listen on TCP port 2345 for a connection
+from the cross gdb.
Then, on the host, you should start the cross gdb using the following +command line:
<buildroot>/output/host/usr/bin/<tuple>-gdb -x <buildroot>/output/staging/usr/share/buildroot/gdbinit foo
Of course, foo must be available in the current directory, built
+with debugging symbols. Typically you start this command from the
+directory where foo is built (and not from output/target/ as the
+binaries in that directory are stripped).
The <buildroot>/output/staging/usr/share/buildroot/gdbinit file will tell the
+cross gdb where to find the libraries of the target.
Finally, to connect to the target from the cross gdb:
(gdb) target remote <target ip address>:2345
ccache is a compiler cache. It stores the +object files resulting from each compilation process, and is able to +skip future compilation of the same source file (with same compiler +and same arguments) by using the pre-existing object files. When doing +almost identical builds from scratch a number of times, it can nicely +speed up the build process.
ccache support is integrated in Buildroot. You just have to enable
+Enable compiler cache in Build options. This will automatically
+build ccache and use it for every host and target compilation.
The cache is located in $HOME/.buildroot-ccache. It is stored
+outside of Buildroot output directory so that it can be shared by
+separate Buildroot builds. If you want to get rid of the cache, simply
+remove this directory.
You can get statistics on the cache (its size, number of hits,
+misses, etc.) by running make ccache-stats.
The make target ccache-options and the CCACHE_OPTIONS variable
+provide more generic access to the ccache. For example
# set cache limit size +make CCACHE_OPTIONS="--max-size=5G" ccache-options + +# zero statistics counters +make CCACHE_OPTIONS="--zero-stats" ccache-options
The various tarballs that are downloaded by Buildroot are all stored
+in BR2_DL_DIR, which by default is the dl directory. If you want
+to keep a complete version of Buildroot which is known to be working
+with the associated tarballs, you can make a copy of this directory.
+This will allow you to regenerate the toolchain and the target
+filesystem with exactly the same versions.
If you maintain several Buildroot trees, it might be better to have a
+shared download location. This can be achieved by pointing the
+BR2_DL_DIR environment variable to a directory. If this is
+set, then the value of BR2_DL_DIR in the Buildroot configuration is
+overridden. The following line should be added to <~/.bashrc>.
$ export BR2_DL_DIR <shared download location>
The download location can also be set in the .config file, with the
+BR2_DL_DIR option. Unlike most options in the .config file, this value
+is overridden by the BR2_DL_DIR environment variable.
Running make <package> builds and installs that particular package
+and its dependencies.
For packages relying on the Buildroot infrastructure, there are +numerous special make targets that can be called independently like +this:
make <package>-<target>
The package build targets are (in the order they are executed):
| command/target | Description |
|---|---|
| Fetch the source (download the tarball, clone +the source repository, etc) |
| Build and install all dependencies required to +build the package |
| Put the source in the package build directory +(extract the tarball, copy the source, etc) |
| Apply the patches, if any |
| Run the configure commands, if any |
| Run the compilation commands |
| target package: Run the installation of the package in the +staging directory, if necessary |
| target package: Run the installation of the package in the +target directory, if necessary |
| target package: Run the 2 previous installation commands +host package: Run the installation of the package in the host +directory |
Additionally, there are some other useful make targets:
| command/target | Description |
|---|---|
| Displays the dependencies required to build the +package |
| Generate a dependency graph of the package, in the +context of the current Buildroot configuration. See +this section +Section 8.8, âGraphing the dependencies between packagesâ for more details about dependency +graphs. |
| Remove the whole package build directory |
| Re-run the install commands |
| Re-run the compilation commands - this only makes
+sense when using the |
| Re-run the configure commands, then rebuild - this only
+makes sense when using the |
The normal operation of Buildroot is to download a tarball, extract
+it, configure, compile and install the software component found inside
+this tarball. The source code is extracted in
+output/build/<package>-<version>, which is a temporary directory:
+whenever make clean is used, this directory is entirely removed, and
+re-recreated at the next make invocation. Even when a Git or
+Subversion repository is used as the input for the package source
+code, Buildroot creates a tarball out of it, and then behaves as it
+normally does with tarballs.
This behavior is well-suited when Buildroot is used mainly as an +integration tool, to build and integrate all the components of an +embedded Linux system. However, if one uses Buildroot during the +development of certain components of the system, this behavior is not +very convenient: one would instead like to make a small change to the +source code of one package, and be able to quickly rebuild the system +with Buildroot.
Making changes directly in output/build/<package>-<version> is not
+an appropriate solution, because this directory is removed on make
+clean.
Therefore, Buildroot provides a specific mechanism for this use case:
+the <pkg>_OVERRIDE_SRCDIR mechanism. Buildroot reads an override
+file, which allows the user to tell Buildroot the location of the
+source for certain packages. By default this override file is named
+local.mk and located in the top directory of the Buildroot source
+tree, but a different location can be specified through the
+BR2_PACKAGE_OVERRIDE_FILE configuration option.
In this override file, Buildroot expects to find lines of the form:
<pkg1>_OVERRIDE_SRCDIR = /path/to/pkg1/sources +<pkg2>_OVERRIDE_SRCDIR = /path/to/pkg2/sources
For example:
LINUX_OVERRIDE_SRCDIR = /home/bob/linux/ +BUSYBOX_OVERRIDE_SRCDIR = /home/bob/busybox/
When Buildroot finds that for a given package, an
+<pkg>_OVERRIDE_SRCDIR has been defined, it will no longer attempt to
+download, extract and patch the package. Instead, it will directly use
+the source code available in in the specified directory and make
+clean will not touch this directory. This allows to point Buildroot
+to your own directories, that can be managed by Git, Subversion, or
+any other version control system. To achieve this, Buildroot will use
+rsync to copy the source code of the component from the specified
+<pkg>_OVERRIDE_SRCDIR to output/build/<package>-custom/.
This mechanism is best used in conjunction with the make
+<pkg>-rebuild and make <pkg>-reconfigure targets. A make
+<pkg>-rebuild all sequence will rsync the source code from
+<pkg>_OVERRIDE_SRCDIR to output/build/<package>-custom (thanks to
+rsync, only the modified files are copied), and restart the build
+process of just this package.
In the example of the linux package above, the developer can then
+make a source code change in /home/bob/linux and then run:
make linux-rebuild all
and in a matter of seconds gets the updated Linux kernel image in
+output/images. Similarly, a change can be made to the BusyBox source
+code in /home/bob/busybox, and after:
make busybox-rebuild all
the root filesystem image in output/images contains the updated
+BusyBox.
Typical actions you may need to perform for a given project are:
- +configuring Buildroot (including build options and toolchain, + bootloader, kernel, package and filesystem image type selection) +
- +configuring other components, like the Linux kernel and BusyBox +
+customizing the generated target filesystem +
-
+adding or overwriting files on the target filesystem (using
+
BR2_ROOTFS_OVERLAY) + -
+modifying or deleting files on the target filesystem (using
+
BR2_ROOTFS_POST_BUILD_SCRIPT) + -
+running arbitrary commands prior to generating the filesystem image
+ (using
BR2_ROOTFS_POST_BUILD_SCRIPT) + -
+setting file permissions and ownership (using
+
BR2_ROOTFS_DEVICE_TABLE) + -
+adding custom devices nodes (using
+
BR2_ROOTFS_STATIC_DEVICE_TABLE) +
-
+adding or overwriting files on the target filesystem (using
+
-
+adding custom user accounts (using
BR2_ROOTFS_USERS_TABLES) + -
+running arbitrary commands after generating the filesystem image
+ (using
BR2_ROOTFS_POST_IMAGE_SCRIPT) + -
+adding project-specific patches to some packages (using
+
BR2_GLOBAL_PATCH_DIR) + - +adding project-specific packages +
An important note regarding such project-specific customizations: +please carefully consider which changes are indeed project-specific and +which changes are also useful to developers outside your project. The +Buildroot community highly recommends and encourages the upstreaming of +improvements, packages and board support to the official Buildroot +project. Of course, it is sometimes not possible or desirable to +upstream because the changes are highly specific or proprietary.
This chapter describes how to make such project-specific customizations +in Buildroot and how to store them in a way that you can build the same +image in a reproducible way, even after running make clean. By +following the recommended strategy, you can even use the same Buildroot +tree to build multiple distinct projects!
When customizing Buildroot for your project, you will be creating one or +more project-specific files that need to be stored somewhere. While most +of these files could be placed in any location as their path is to be +specified in the Buildroot configuration, the Buildroot developers +recommend a specific directory structure which is described in this +section.
Orthogonal to this directory structure, you can choose where you place
+this structure itself: either inside the Buildroot tree, or outside of
+it using BR2_EXTERNAL. Both options are valid, the choice is up to you.
+-- board/ +| +-- <company>/ +| +-- <boardname>/ +| +-- linux.config +| +-- busybox.config +| +-- <other configuration files> +| +-- post_build.sh +| +-- post_image.sh +| +-- rootfs_overlay/ +| | +-- etc/ +| | +-- <some file> +| +-- patches/ +| +-- foo/ +| | +-- <some patch> +| +-- libbar/ +| +-- <some other patches> +| ++-- configs/ +| +-- <boardname>_defconfig +| ++-- package/ +| +-- <company>/ +| +-- Config.in (if not using BR2_EXTERNAL) +| +-- <company>.mk (if not using BR2_EXTERNAL) +| +-- package1/ +| | +-- Config.in +| | +-- package1.mk +| +-- package2/ +| +-- Config.in +| +-- package2.mk +| ++-- Config.in (if using BR2_EXTERNAL) ++-- external.mk (if using BR2_EXTERNAL)
Details on the files shown above are given further in this chapter.
Note: if you choose to place this structure outside of the Buildroot
+tree using BR2_EXTERNAL, the <company> and possibly <boardname>
+components may be superfluous and can be left out.
It is quite common for a user to have several related projects that partly +need the same customizations. Instead of duplicating these +customizations for each project, it is recommended to use a layered +customization approach, as explained in this section.
Almost all of the customization methods available in Buildroot, like
+post-build scripts and root filesystem overlays, accept a
+space-separated list of items. The specified items are always treated in
+order, from left to right. By creating more than one such item, one for
+the common customizations and another one for the really
+project-specific customizations, you can avoid unnecessary duplication.
+Each layer is typically embodied by a separate directory inside
+board/<company>/. Depending on your projects, you could even introduce
+more than two layers.
An example directory structure for where a user has two customization +layers common and fooboard is:
+-- board/ + +-- <company>/ + +-- common/ + | +-- post_build.sh + | +-- rootfs_overlay/ + | | +-- ... + | +-- patches/ + | +-- ... + | + +-- fooboard/ + +-- linux.config + +-- busybox.config + +-- <other configuration files> + +-- post_build.sh + +-- rootfs_overlay/ + | +-- ... + +-- patches/ + +-- ...
For example, if the user has the BR2_GLOBAL_PATCH_DIR configuration
+option set as:
BR2_GLOBAL_PATCH_DIR="board/<company>/common/patches board/<company>/fooboard/patches"
then first the patches from the common layer would be applied, +followed by the patches from the fooboard layer.
As already briefly mentioned in Section 9.1, âRecommended directory structureâ, you can +place project-specific customizations in two locations:
- +directly within the Buildroot tree, typically maintaining them using + branches in a version control system so that upgrading to a newer + Buildroot release is easy. +
-
+outside of the Buildroot tree, using the
BR2_EXTERNALmechanism. + This mechanism allows to keep package recipes, board support and + configuration files outside of the Buildroot tree, while still + having them nicely integrated in the build logic. This section + explains how to useBR2_EXTERNAL. +
BR2_EXTERNAL is an environment variable that can be used to point to
+a directory that contains Buildroot customizations. It can be passed
+to any Buildroot make invocation. It is automatically saved in the
+hidden .br-external file in the output directory. Thanks to this,
+there is no need to pass BR2_EXTERNAL at every make invocation. It
+can however be changed at any time by passing a new value, and can be
+removed by passing an empty value.
Note. The BR2_EXTERNAL path can be either an absolute or a relative path,
+but if itâs passed as a relative path, it is important to note that it
+is interpreted relative to the main Buildroot source directory, not
+to the Buildroot output directory.
Some examples:
buildroot/ $ make BR2_EXTERNAL=/path/to/foobar menuconfig
From now on, external definitions from the /path/to/foobar
+directory will be used:
buildroot/ $ make +buildroot/ $ make legal-info
We can switch to another external definitions directory at any time:
buildroot/ $ make BR2_EXTERNAL=/where/we/have/barfoo xconfig
Or disable the usage of external definitions:
buildroot/ $ make BR2_EXTERNAL= xconfig
BR2_EXTERNAL allows three different things:
-
+One can store all the board-specific configuration files there,
+ such as the kernel configuration, the root filesystem overlay, or
+ any other configuration file for which Buildroot allows to set its
+ location. The
BR2_EXTERNALvalue is available within the + Buildroot configuration using$(BR2_EXTERNAL). As an example, one + could set theBR2_ROOTFS_OVERLAYBuildroot option to +$(BR2_EXTERNAL)/board/<boardname>/overlay/(to specify a root + filesystem overlay), or theBR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE+ Buildroot option to +$(BR2_EXTERNAL)/board/<boardname>/kernel.config(to specify the + location of the kernel configuration file). + +One can store package recipes (i.e.
Config.inand +<packagename>.mk), or even custom configuration options and make + logic. Buildroot automatically includes$(BR2_EXTERNAL)/Config.into + make it appear in the top-level configuration menu, and includes +$(BR2_EXTERNAL)/external.mkwith the rest of the makefile logic. +Note. Providing
Config.inandexternal.mkis mandatory, but they can be + empty.The main usage of this is to store package recipes. The recommended + way to do this is to write a
$(BR2_EXTERNAL)/Config.infile that + looks like:source "$BR2_EXTERNAL/package/package1/Config.in" +source "$BR2_EXTERNAL/package/package2/Config.in"
Then, have a
$(BR2_EXTERNAL)/external.mkfile that looks like:include $(sort $(wildcard $(BR2_EXTERNAL)/package/*/*.mk))
And then in
$(BR2_EXTERNAL)/package/package1and +$(BR2_EXTERNAL)/package/package2create normal Buildroot + package recipes, as explained in Chapter 17, Adding new packages to Buildroot. + If you prefer, you can also group the packages in subdirectories + called <boardname> and adapt the above paths accordingly.-
+One can store Buildroot defconfigs in the
configssubdirectory of +$(BR2_EXTERNAL). Buildroot will automatically show them in the + output ofmake list-defconfigsand allow them to be loaded with the + normalmake <name>_defconfigcommand. They will be visible under the +User-provided configs' label in the make list-defconfigs output. +
The Buildroot configuration can be stored using the command
+ make savedefconfig.
This strips the Buildroot configuration down by removing configuration
+options that are at their default value. The result is stored in a file
+called defconfig. If you want to save it in another place, change the
+BR2_DEFCONFIG option in the Buildroot configuration itself, or call
+make with make savedefconfig BR2_DEFCONFIG=<path-to-defconfig>.
The recommended place to store this defconfig is
+configs/<boardname>_defconfig. If you follow this recommendation, the
+configuration will be listed in make help and can be set again by
+running make <boardname>_defconfig.
Alternatively, you can copy the file to any other place and rebuild with
+make defconfig BR2_DEFCONFIG=<path-to-defconfig-file>.
The configuration files for BusyBox, the Linux kernel, Barebox and
+uClibc should be stored as well if changed. For each of these
+components, a Buildroot configuration option exists to point to an input
+configuration file, e.g. BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE. To store
+their configuration, set these configuration options to a path where you
+want to save the configuration files, and then use the helper targets
+described below to actually store the configuration.
As explained in Section 9.1, âRecommended directory structureâ, the recommended path to
+store these configuration files is
+board/<company>/<boardname>/foo.config.
Make sure that you create a configuration file before changing
+the BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE etc. options. Otherwise,
+Buildroot will try to access this config file, which doesnât exist
+yet, and will fail. You can create the configuration file by running
+make linux-menuconfig etc.
Buildroot provides a few helper targets to make the saving of +configuration files easier.
-
+
make linux-update-defconfigsaves the linux configuration to the + path specified byBR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE. It + simplifies the config file by removing default values. However, + this only works with kernels starting from 2.6.33. For earlier + kernels, usemake linux-update-config. + -
+
make busybox-update-configsaves the busybox configuration to the + path specified byBR2_PACKAGE_BUSYBOX_CONFIG. + -
+
make uclibc-update-configsaves the uClibc configuration to the + path specified byBR2_UCLIBC_CONFIG. + -
+
make barebox-update-defconfigsaves the barebox configuration to the + path specified byBR2_TARGET_BAREBOX_CUSTOM_CONFIG_FILE. + -
+For at91bootstrap3, no helper exists so you have to copy the config
+ file manually to
BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_CONFIG_FILE. +
Besides changing the configuration through make *config,
+there are a few other ways to customize the resulting target filesystem.
The two recommended methods, which can co-exist, are root filesystem +overlay(s) and post build script(s).
-
+Root filesystem overlays (
BR2_ROOTFS_OVERLAY) + A filesystem overlay is a tree of files that is copied directly + over the target filesystem after it has been built. To enable this + feature, set config option
BR2_ROOTFS_OVERLAY(in theSystem + configurationmenu) to the root of the overlay. You can even specify + multiple overlays, space-separated. If you specify a relative path, + it will be relative to the root of the Buildroot tree. Hidden + directories of version control systems, like.git,.svn,.hg, + etc., files called.emptyand files ending in~are excluded from + the copy.As shown in Section 9.1, âRecommended directory structureâ, the recommended path for + this overlay is
board/<company>/<boardname>/rootfs-overlay.-
+Post-build scripts (
BR2_ROOTFS_POST_BUILD_SCRIPT) + Post-build scripts are shell scripts called after Buildroot builds + all the selected software, but before the rootfs images are + assembled. To enable this feature, specify a space-separated list of + post-build scripts in config option
BR2_ROOTFS_POST_BUILD_SCRIPT(in + theSystem configurationmenu). If you specify a relative path, it + will be relative to the root of the Buildroot tree.Using post-build scripts, you can remove or modify any file in your + target filesystem. You should, however, use this feature with care. + Whenever you find that a certain package generates wrong or unneeded + files, you should fix that package rather than work around it with some + post-build cleanup scripts.
As shown in Section 9.1, âRecommended directory structureâ, the recommended path for + this script is
board/<company>/<boardname>/post_build.sh.The post-build scripts are run with the main Buildroot tree as current + working directory. The path to the target filesystem is passed as the + first argument to each script. If the config option +
BR2_ROOTFS_POST_SCRIPT_ARGSis not empty, these arguments will be + passed to the script too. All the scripts will be passed the exact + same set of arguments, it is not possible to pass different sets of + arguments to each script.In addition, you may also use these environment variables:
-
+
BR2_CONFIG: the path to the Buildroot .config file + -
+
HOST_DIR,STAGING_DIR,TARGET_DIR: see + Section 17.5.2, âgeneric-packagereferenceâ + -
+
BUILD_DIR: the directory where packages are extracted and built + -
+
BINARIES_DIR: the place where all binary files (aka images) are + stored + -
+
BASE_DIR: the base output directory +
-
+
Below two more methods of customizing the target filesystem are +described, but they are not recommended.
- +Direct modification of the target filesystem +
For temporary modifications, you can modify the target filesystem + directly and rebuild the image. The target filesystem is available + under
output/target/. After making your changes, runmaketo + rebuild the target filesystem image.This method allows you to do anything to the target filesystem, but if + you need to clean your Buildroot tree using
make clean, these + changes will be lost. Such cleaning is necessary in several cases, + refer to Section 8.2, âUnderstanding when a full rebuild is necessaryâ for details. This solution is therefore + only useful for quick tests: changes do not survive themake clean+ command. Once you have validated your changes, you should make sure + that they will persist after amake clean, using a root filesystem + overlay or a post-build script.-
+Custom target skeleton (
BR2_ROOTFS_SKELETON_CUSTOM) + The root filesystem image is created from a target skeleton, on top of + which all packages install their files. The skeleton is copied to the + target directory
output/targetbefore any package is built and + installed. The default target skeleton provides the standard Unix + filesystem layout and some basic init scripts and configuration files.If the default skeleton (available under
system/skeleton) does not + match your needs, you would typically use a root filesystem overlay or + post-build script to adapt it. However, if the default skeleton is + entirely different than what you need, using a custom skeleton may be + more suitable.To enable this feature, enable config option +
BR2_ROOTFS_SKELETON_CUSTOMand setBR2_ROOTFS_SKELETON_CUSTOM_PATH+ to the path of your custom skeleton. Both options are available in the +System configurationmenu. If you specify a relative path, it will + be relative to the root of the Buildroot tree.This method is not recommended because it duplicates the entire + skeleton, which prevents taking advantage of the fixes or improvements + brought to the default skeleton in later Buildroot releases.
Sometimes it is needed to set specific permissions or ownership on files +or device nodes. For example, certain files may need to be owned by +root. Since the post-build scripts are not run as root, you cannot do +such changes from there unless you use an explicit fakeroot from the +post-build script.
Instead, Buildroot provides support for so-called permission tables.
+To use this feature, set config option BR2_ROOTFS_DEVICE_TABLE to a
+space-separated list of permission tables, regular text files following
+the makedev syntax
+Chapter 22, Makedev syntax documentation.
If you are using a static device table (i.e. not using devtmpfs,
+mdev, or (e)udev) then you can add device nodes using the same
+syntax, in so-called device tables. To use this feature, set config
+option BR2_ROOTFS_STATIC_DEVICE_TABLE to a space-separated list of
+device tables.
As shown in Section 9.1, âRecommended directory structureâ, the recommended location for
+such files is board/<company>/<boardname>/.
It should be noted that if the specific permissions or device nodes are
+related to a specific application, you should set variables
+FOO_PERMISSIONS and FOO_DEVICES in the packageâs .mk file instead
+(see Section 17.5.2, âgeneric-package referenceâ).
Sometimes it is needed to add specific users in the target system.
+To cover this requirement, Buildroot provides support for so-called
+users tables. To use this feature, set config option
+BR2_ROOTFS_USERS_TABLES to a space-separated list of users tables,
+regular text files following the makeusers syntax
+Chapter 23, Makeusers syntax documentation.
As shown in Section 9.1, âRecommended directory structureâ, the recommended location for
+such files is board/<company>/<boardname>/.
It should be noted that if the custom users are related to a specific
+application, you should set variable FOO_USERS in the packageâs .mk
+file instead (see Section 17.5.2, âgeneric-package referenceâ).
While post-build scripts (Section 9.5, âCustomizing the generated target filesystemâ) are run before +building the filesystem image, kernel and bootloader, post-image +scripts can be used to perform some specific actions after all images +have been created.
Post-image scripts can for example be used to automatically extract your +root filesystem tarball in a location exported by your NFS server, or +to create a special firmware image that bundles your root filesystem and +kernel image, or any other custom action required for your project.
To enable this feature, specify a space-separated list of post-image
+scripts in config option BR2_ROOTFS_POST_IMAGE_SCRIPT (in the System
+configuration menu). If you specify a relative path, it will be
+relative to the root of the Buildroot tree.
Just like post-build scripts, post-image scripts are run with the main
+Buildroot tree as current working directory. The path to the images
+output directory is passed as the first argument to each script. If the
+config option BR2_ROOTFS_POST_SCRIPT_ARGS is not empty, these
+arguments will be passed to the script too. All the scripts will be
+passed the exact same set of arguments, it is not possible to pass
+different sets of arguments to each script.
Again just like for the post-build scripts, the scripts have access to
+the environment variables BR2_CONFIG, HOST_DIR, STAGING_DIR,
+TARGET_DIR, BUILD_DIR, BINARIES_DIR and BASE_DIR.
The post-image scripts will be executed as the user that executes +Buildroot, which should normally not be the root user. Therefore, any +action requiring root permissions in one of these scripts will require +special handling (usage of fakeroot or sudo), which is left to the +script developer.
It is sometimes useful to apply extra patches to packages - on top of +those provided in Buildroot. This might be used to support custom +features in a project, for example, or when working on a new +architecture.
The BR2_GLOBAL_PATCH_DIR configuration option can be used to specify
+a space separated list of one or more directories containing package
+patches.
For a specific version <packageversion> of a specific package
+<packagename>, patches are applied from BR2_GLOBAL_PATCH_DIR as
+follows:
+For every directory -
<global-patch-dir>- that exists in +BR2_GLOBAL_PATCH_DIR, a<package-patch-dir>will be determined as + follows: +-
+
<global-patch-dir>/<packagename>/<packageversion>/if the + directory exists. + -
+Otherwise,
<global-patch-dir>/<packagename>if the directory + exists. +
-
+
+Patches will then be applied from a
<package-patch-dir>as + follows: +-
+If a
seriesfile exists in the package directory, then patches are + applied according to theseriesfile; + -
+Otherwise, patch files matching
*.patchare applied in + alphabetical order. So, to ensure they are applied in the right + order, it is highly recommended to name the patch files like this: +<number>-<description>.patch, where<number>refers to the + apply order. +
-
+If a
For information about how patches are applied for a package, see +Section 18.2, âHow patches are appliedâ
The BR2_GLOBAL_PATCH_DIR option is the preferred method for
+specifying a custom patch directory for packages. It can be used to
+specify a patch directory for any package in buildroot. It should also
+be used in place of the custom patch directory options that are
+available for packages such as U-Boot and Barebox. By doing this, it
+will allow a user to manage their patches from one top-level
+directory.
The exception to BR2_GLOBAL_PATCH_DIR being the preferred method for
+specifying custom patches is BR2_LINUX_KERNEL_PATCH.
+BR2_LINUX_KERNEL_PATCH should be used to specify kernel patches that
+are available at an URL. Note: BR2_LINUX_KERNEL_PATCH specifies kernel
+patches that are applied after patches available in BR2_GLOBAL_PATCH_DIR,
+as it is done from a post-patch hook of the Linux package.
In general, any new package should be added directly in the package
+directory and submitted to the Buildroot upstream project. How to add
+packages to Buildroot in general is explained in full detail in
+Chapter 17, Adding new packages to Buildroot and will not be repeated here. However, your
+project may need some proprietary packages that cannot be upstreamed.
+This section will explain how you can keep such project-specific
+packages in a project-specific directory.
As shown in Section 9.1, âRecommended directory structureâ, the recommended location for
+project-specific packages is package/<company>/. If you are using the
+BR2_EXTERNAL feature (see Section 9.2, âKeeping customizations outside of Buildrootâ) the recommended
+location is $(BR2_EXTERNAL)/package/.
However, Buildroot will not be aware of the packages in this location,
+unless we perform some additional steps. As explained in
+Chapter 17, Adding new packages to Buildroot, a package in Buildroot basically consists of two
+files: a .mk file (describing how to build the package) and a
+Config.in file (describing the configuration options for this
+package).
Buildroot will automatically include the .mk files in first-level
+subdirectories of the package directory (using the pattern
+package/*/*.mk). If we want Buildroot to include .mk files from
+deeper subdirectories (like package/<company>/package1/) then we
+simply have to add a .mk file in a first-level subdirectory that
+includes these additional .mk files. Therefore, create a file
+package/<company>/<company>.mk with following contents (assuming you
+have only one extra directory level below package/<company>/):
include $(sort $(wildcard package/<company>/*/*.mk))
If you are using BR2_EXTERNAL, create a file
+$(BR2_EXTERNAL)/external.mk with following contents (again assuming only
+one extra level):
include $(sort $(wildcard $(BR2_EXTERNAL)/package/*/*.mk))
For the Config.in files, create a file package/<company>/Config.in
+that includes the Config.in files of all your packages. An exhaustive
+list has to be provided since wildcards are not supported in the source command of kconfig.
+For example:
source "package/<company>/package1/Config.in" +source "package/<company>/package2/Config.in"
Include this new file package/<company>/Config.in from
+package/Config.in, preferably in a company-specific menu to make
+merges with future Buildroot versions easier.
If you are using BR2_EXTERNAL, create a file
+$(BR2_EXTERNAL)/Config.in with similar contents:
source "$BR2_EXTERNAL/package/package1/Config.in" +source "$BR2_EXTERNAL/package/package2/Config.in"
You do not have to add an include for this $(BR2_EXTERNAL)/Config.in
+file as it is included automatically.
Earlier in this chapter, the different methods for making +project-specific customizations have been described. This section will +now summarize all this by providing step-by-step instructions to storing your +project-specific customizations. Clearly, the steps that are not relevant to +your project can be skipped.
-
+
make menuconfigto configure toolchain, packages and kernel. + -
+
make linux-menuconfigto update the kernel config, similar for + other configuration like busybox, uclibc, ⦠+ -
+
mkdir -p board/<manufacturer>/<boardname>+ +Set the following options to
board/<manufacturer>/<boardname>/<package>.config+ (as far as they are relevant): +-
+
BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE+ -
+
BR2_PACKAGE_BUSYBOX_CONFIG+ -
+
BR2_UCLIBC_CONFIG+ -
+
BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_CONFIG_FILE+ -
+
BR2_TARGET_BAREBOX_CUSTOM_CONFIG_FILE+
-
+
+Write the configuration files: +
-
+
make linux-update-defconfig+ -
+
make busybox-update-config+ -
+
make uclibc-update-config+ -
+
cp <output>/build/at91bootstrap3-*/.config + board/<manufacturer>/<boardname>/at91bootstrap3.config+ -
+
make barebox-update-defconfig+
-
+
-
+Create
board/<manufacturer>/<boardname>/rootfs-overlay/and fill it + with additional files you need on your rootfs, e.g. +board/<manufacturer>/<boardname>/rootfs-overlay/etc/inittab. + SetBR2_ROOTFS_OVERLAY+ toboard/<manufacturer>/<boardname>/rootfs-overlay. + -
+Create a post-build script
+
board/<manufacturer>/<boardname>/post_build.sh. Set +BR2_ROOTFS_POST_BUILD_SCRIPTto +board/<manufacturer>/<boardname>/post_build.sh+ -
+If additional setuid permissions have to be set or device nodes have
+ to be created, create
board/<manufacturer>/<boardname>/device_table.txt+ and add that path toBR2_ROOTFS_DEVICE_TABLE. + -
+If additional user accounts have to be created, create
+
board/<manufacturer>/<boardname>/users_table.txtand add that path + toBR2_ROOTFS_USERS_TABLES. + -
+To add custom patches to certain packages, set
BR2_GLOBAL_PATCH_DIR+ toboard/<manufacturer>/<boardname>/patches/and add your patches + for each package in a subdirectory named after the package. Each + patch should be called<packagename>-<num>-<description>.patch. + -
+Specifically for the Linux kernel, there also exists the option
+
BR2_LINUX_KERNEL_PATCHwith as main advantage that it can also + download patches from a URL. If you do not need this, +BR2_GLOBAL_PATCH_DIRis preferred. U-Boot, Barebox, at91bootstrap + and at91bootstrap3 also have separate options, but these do not + provide any advantage overBR2_GLOBAL_PATCH_DIRand will likely be + removed in the future. + -
+If you need to add project-specific packages, create
+
package/<manufacturer>/and place your packages in that + directory. Create an overall<manufacturer>.mkfile that + includes the.mkfiles of all your packages. Create an overall +Config.infile that sources theConfig.infiles of all your + packages. Include thisConfig.infile from Buildrootâs +package/Config.infile. + -
+
make savedefconfigto save the buildroot configuration. + -
+
cp defconfig configs/<boardname>_defconfig+
If the boot process seems to hang after the following messages +(messages not necessarily exactly similar, depending on the list of +packages selected):
Freeing init memory: 3972K +Initializing random number generator... done. +Starting network... +Starting dropbear sshd: generating rsa key... generating dsa key... OK
then it means that your system is running, but didnât start a shell on
+the serial console. In order to have the system start a shell on your
+serial console, you have to go into the Buildroot configuration, in
+System configuration, modify Run a getty (login prompt) after boot
+and set the appropriate port and baud rate in the getty options
+submenu. This will automatically tune the /etc/inittab file of the
+generated system so that a shell starts on the correct serial port.
It has been decided that support for the native compiler on the +target would be stopped from the Buildroot-2012.11 release because:
- +this feature was neither maintained nor tested, and often broken; +
- +this feature was only available for Buildroot toolchains; +
- +Buildroot mostly targets small or very small target hardware + with limited resource onboard (CPU, ram, mass-storage), for which + compiling on the target does not make much sense; +
- +Buildroot aims at easing the cross-compilation, making native + compilation on the target unnecessary. +
If you need a compiler on your target anyway, then Buildroot is not +suitable for your purpose. In such case, you need a real +distribution and you should opt for something like:
- +openembedded +
- +yocto +
- +emdebian +
- +Fedora +
- +openSUSE ARM +
- +Arch Linux ARM +
- +⦠+
Since there is no compiler available on the target (see +Section 10.2, âWhy is there no compiler on the target?â), it does not make sense to waste +space with headers or static libraries.
Therefore, those files are always removed from the target since the +Buildroot-2012.11 release.
Because Buildroot mostly targets small or very small target +hardware with limited resource onboard (CPU, ram, mass-storage), it +does not make sense to waste space with the documentation data.
If you need documentation data on your target anyway, then Buildroot +is not suitable for your purpose, and you should look for a real +distribution (see: Section 10.2, âWhy is there no compiler on the target?â).
If a package exists in the Buildroot tree and does not appear in the +config menu, this most likely means that some of the packageâs +dependencies are not met.
To know more about the dependencies of a package, search for the +package symbol in the config menu (see Section 8.1, âmake tipsâ).
Then, you may have to recursively enable several options (which +correspond to the unmet dependencies) to finally be able to select +the package.
If the package is not visible due to some unmet toolchain options, +then you should certainly run a full rebuild (see Section 8.1, âmake tipsâ for +more explanations).
There are plenty of reasons to not use the target directory a chroot +one, among these:
- +file ownerships, modes and permissions are not correctly set in the + target directory; +
- +device nodes are not created in the target directory. +
For these reasons, commands run through chroot, using the target +directory as the new root, will most likely fail.
If you want to run the target filesystem inside a chroot, or as an NFS
+root, then use the tarball image generated in images/ and extract it
+as root.
One feature that is often discussed on the Buildroot list is the +general topic of "package management". To summarize, the idea +would be to add some tracking of which Buildroot package installs +what files, with the goals of:
- +being able to remove files installed by a package when this package + gets unselected from the menuconfig; +
- +being able to generate binary packages (ipk or other format) that + can be installed on the target without re-generating a new root + filesystem image. +
In general, most people think it is easy to do: just track which package +installed what and remove it when the package is unselected. However, it +is much more complicated than that:
-
+It is not only about the
target/directory, but also the sysroot in +host/usr/<tuple>/sysrootand thehost/directory itself. All files + installed in those directories by various packages must be tracked. + - +When a package is unselected from the configuration, it is not + sufficient to remove just the files it installed. One must also + remove all its reverse dependencies (i.e. packages relying on it) + and rebuild all those packages. For example, package A depends + optionally on the OpenSSL library. Both are selected, and Buildroot + is built. Package A is built with crypto support using OpenSSL. + Later on, OpenSSL gets unselected from the configuration, but + package A remains (since OpenSSL is an optional dependency, this + is possible.) If only OpenSSL files are removed, then the files + installed by package A are broken: they use a library that is no + longer present on the target. Although this is technically doable, + it adds a lot of complexity to Buildroot, which goes against the + simplicity we try to stick to. +
- +In addition to the previous problem, there is the case where the + optional dependency is not even known to Buildroot. For example, + package A in version 1.0 never used OpenSSL, but in version 2.0 it + automatically uses OpenSSL if available. If the Buildroot .mk file + hasnât been updated to take this into account, then package A will + not be part of the reverse dependencies of OpenSSL and will not be + removed and rebuilt when OpenSSL is removed. For sure, the .mk file + of package A should be fixed to mention this optional dependency, + but in the mean time, you can have non-reproducible behaviors. +
- +The request is to also allow changes in the menuconfig to be + applied on the output directory without having to rebuild + everything from scratch. However, this is very difficult to achieve + in a reliable way: what happens when the suboptions of a package + are changed (we would have to detect this, and rebuild the package + from scratch and potentially all its reverse dependencies), what + happens if toolchain options are changed, etc. At the moment, what + Buildroot does is clear and simple so its behaviour is very + reliable and it is easy to support users. If configuration changes + done in menuconfig are applied after the next make, then it has to + work correctly and properly in all situations, and not have some + bizarre corner cases. The risk is to get bug reports like "I have + enabled package A, B and C, then ran make, then disabled package + C and enabled package D and ran make, then re-enabled package C + and enabled package E and then there is a build failure". Or worse + "I did some configuration, then built, then did some changes, + built, some more changes, built, some more changes, built, and now + it fails, but I donât remember all the changes I did and in which + order". This will be impossible to support. +
For all these reasons, the conclusion is that adding tracking of +installed files to remove them when the package is unselected, or to +generate a repository of binary packages, is something that is very +hard to achieve reliably and will add a lot of complexity.
On this matter, the Buildroot developers make this position statement:
- +Buildroot strives to make it easy to generate a root filesystem (hence + the name, by the way.) That is what we want to make Buildroot good at: + building root filesystems. +
- +Buildroot is not meant to be a distribution (or rather, a distribution + generator.) It is the opinion of most Buildroot developers that this + is not a goal we should pursue. We believe that there are other tools + better suited to generate a distro than Buildroot is. For example, + Open Embedded, or openWRT, + are such tools. +
- +We prefer to push Buildroot in a direction that makes it easy (or even + easier) to generate complete root filesystems. This is what makes + Buildroot stands out in the crowd (among other things, of course!) +
- +We believe that for most embedded Linux systems, binary packages are + not necessary, and potentially harmful. When binary packages are + used, it means that the system can be partially upgraded, which + creates an enormous number of possible combinations of package + versions that should be tested before doing the upgrade on the + embedded device. On the other hand, by doing complete system + upgrades by upgrading the entire root filesystem image at once, + the image deployed to the embedded system is guaranteed to really + be the one that has been tested and validated. +
Since Buildroot often involves doing full rebuilds of the entire +system that can be quite long, we provide below a number of tips to +help reduce the build time:
- +Use a pre-built external toolchain instead of the default Buildroot + internal toolchain. By using a pre-built Linaro toolchain (on ARM) + or a Sourcery CodeBench toolchain (for ARM, x86, x86-64, MIPS, + etc.), you will save the build time of the toolchain at each + complete rebuild, approximately 15 to 20 minutes. Note that + temporarily using an external toolchain does not prevent you to + switch back to an internal toolchain (that may provide a higher + level of customization) once the rest of your system is working; +
-
+Use the
ccachecompiler cache (see: Section 8.11.3, âUsingccachein Buildrootâ); + - +Learn about rebuilding only the few packages you actually care + about (see Section 8.3, âUnderstanding how to rebuild packagesâ), but beware that sometimes full + rebuilds are anyway necessary (see Section 8.2, âUnderstanding when a full rebuild is necessaryâ); +
- +Make sure you are not using a virtual machine for the Linux system + used to run Buildroot. Most of the virtual machine technologies are + known to cause a significant performance impact on I/O, which is + really important for building source code; +
- +Make sure that youâre using only local files: do not attempt to do + a build over NFS, which significantly slows down the build. Having + the Buildroot download folder available locally also helps a bit. +
- +Buy new hardware. SSDs and lots of RAM are key to speeding up the + builds. +
-
+It is not possible to pass extra linker options via
BR2_TARGET_LDFLAGS+ if such options contain a$sign. For example, the following is known + to break:BR2_TARGET_LDFLAGS="-Wl,-rpath='$ORIGIN/../lib'"+ -
+The
ltp-testsuitepackage does not build with the default uClibc + configuration used by the Buildroot toolchain backend. The LTP + testsuite uses several functions that are considered obsolete, such + as sigset() and others. uClibc configuration options such as + DO_XSI_MATH, UCLIBC_HAS_OBSOLETE_BSD_SIGNAL and + UCLIBC_SV4_DEPRECATED are needed if one wants to build the +ltp-testsuitepackage with uClibc. You need to either use a glibc + or eglibc based toolchain, or enable the appropriate options in the + uClibc configuration. + -
+The
xfsprogspackage does not build with the default uClibc + configuration used by the Buildroot toolchain backend. You need to + either use a glibc or eglibc based toolchain, or enable the + appropriate options in the uClibc configuration. + -
+The
mroutedpackage does not build with the default uClibc + configuration used by the Buildroot toolchain backend. You need to + either use a glibc or eglibc based toolchain, or enable the + appropriate options in the uClibc configuration. + -
+The
libffipackage is not supported on the SuperH 2 and ARC + architectures. + -
+The
prboompackage triggers a compiler failure with the SuperH 4 + compiler from Sourcery CodeBench, version 2012.09. +
All of the end products of Buildroot (toolchain, root filesystem, kernel, +bootloaders) contain open source software, released under various licenses.
Using open source software gives you the freedom to build rich embedded +systems, choosing from a wide range of packages, but also imposes some +obligations that you must know and honour. +Some licenses require you to publish the license text in the documentation of +your product. Others require you to redistribute the source code of the +software to those that receive your product.
The exact requirements of each license are documented in each package, and
+it is your responsibility (or that of your legal office) to comply with those
+requirements.
+To make this easier for you, Buildroot can collect for you some material you
+will probably need. To produce this material, after you have configured
+Buildroot with make menuconfig, make xconfig or make gconfig, run:
make legal-info
Buildroot will collect legally-relevant material in your output directory,
+under the legal-info/ subdirectory.
+There you will find:
-
+A
READMEfile, that summarizes the produced material and contains warnings + about material that Buildroot could not produce. + -
+
buildroot.config: this is the Buildroot configuration file that is usually + produced withmake menuconfig, and which is necessary to reproduce the + build. + -
+The source code for all packages; this is saved in the
sources/and +host-sources/subdirectories for target and host packages respectively. + The source code for packages that set<PKG>_REDISTRIBUTE = NOwill not be + saved. + Patches applied to some packages by Buildroot are distributed with the + Buildroot sources and are not duplicated in thesources/andhost-sources/+ subdirectories. + - +A manifest file (one for host and one for target packages) listing the + configured packages, their version, license and related information. + Some of this information might not be defined in Buildroot; such items are + marked as "unknown". +
-
+The license texts of all packages, in the
licenses/andhost-licenses/+ subdirectories for target and host packages respectively. + If the license file(s) are not defined in Buildroot, the file is not produced + and a warning in theREADMEindicates this. +
Please note that the aim of the legal-info feature of Buildroot is to
+produce all the material that is somehow relevant for legal compliance with the
+package licenses. Buildroot does not try to produce the exact material that
+you must somehow make public. Certainly, more material is produced than is
+needed for a strict legal compliance. For example, it produces the source code
+for packages released under BSD-like licenses, that you are not required to
+redistribute in source form.
Moreover, due to technical limitations, Buildroot does not produce some
+material that you will or may need, such as the toolchain source code and the
+Buildroot source code itself (including patches to packages for which source
+distribution is required).
+When you run make legal-info, Buildroot produces warnings in the README
+file to inform you of relevant material that could not be saved.
Here is a list of the licenses that are most widely used by packages in +Buildroot, with the name used in the manifest files:
-
+
GPLv2: + + GNU General Public License, version 2; + -
+
GPLv2+: + + GNU General Public License, version 2 + or (at your option) any later version; + -
+
GPLv3: + + GNU General Public License, version 3; + -
+
GPLv3+: + + GNU General Public License, version 3 + or (at your option) any later version; + -
+
GPL: + + GNU General Public License (any version); + -
+
LGPLv2: + + GNU Library General Public License, version 2; + -
+
LGPLv2+: + + GNU Library General Public License, version 2 + or (at your option) any later version; + -
+
LGPLv2.1: + + GNU Lesser General Public License, version 2.1; + -
+
LGPLv2.1+: + + GNU Lesser General Public License, version 2.1 + or (at your option) any later version; + -
+
LGPLv3: + + GNU Lesser General Public License, version 3; + -
+
LGPLv3+: + + GNU Lesser General Public License, version 3 + or (at your option) any later version; + -
+
LGPL: + + GNU Lesser General Public License (any version); + -
+
BSD-4c: + + Original BSD 4-clause license; + -
+
BSD-3c: + + BSD 3-clause license; + -
+
BSD-2c: + + BSD 2-clause license; + -
+
MIT: + + MIT-style license; + -
+
Apache-2.0: + + Apache License, version 2.0; +
Buildroot itself is an open source software, released under the +GNU General Public +License, version 2 or (at your option) any later version. +However, being a build system, it is not normally part of the end product: +if you develop the root filesystem, kernel, bootloader or toolchain for a +device, the code of Buildroot is only present on the development machine, not +in the device storage.
Nevertheless, the general view of the Buildroot developers is that you should +release the Buildroot source code along with the source code of other packages +when releasing a product that contains GPL-licensed software. +This is because the +GNU GPL +defines the "complete source code" for an executable work as "all the +source code for all modules it contains, plus any associated interface +definition files, plus the scripts used to control compilation and installation +of the executable". +Buildroot is part of the scripts used to control compilation and +installation of the executable, and as such it is considered part of the +material that must be redistributed.
Keep in mind that this is only the Buildroot developers' opinion, and you +should consult your legal department or lawyer in case of any doubt.
To achieve NFS-boot, enable tar root filesystem in the Filesystem +images menu.
After a complete build, just run the following commands to setup the +NFS-root directory:
sudo tar -xavf /path/to/output_dir/rootfs.tar -C /path/to/nfs_root_dir
Remember to add this path to /etc/exports.
Then, you can execute a NFS-boot from your target.
If you want to chroot in a generated image, then there are few thing +you should be aware of:
- +you should setup the new root from the tar root filesystem image; +
-
+either the selected target architecture is compatible with your host
+ machine, or you should use some
qemu-*binary and correctly set it + within thebinfmtproperties to be able to run the binaries built + for the target on your host machine; + -
+Buildroot does not currently provide
host-qemuandbinfmt+ correctly built and set for that kind of use. +
As mentioned above, Buildroot is basically a set of Makefiles that
+download, configure, and compile software with the correct options. It
+also includes patches for various software packages - mainly the ones
+involved in the cross-compilation toolchain (gcc, binutils and
+uClibc).
There is basically one Makefile per software package, and they are
+named with the .mk extension. Makefiles are split into many different
+parts.
-
+The
toolchain/directory contains the Makefiles + and associated files for all software related to the + cross-compilation toolchain:binutils,gcc,gdb, +kernel-headersanduClibc. + -
+The
arch/directory contains the definitions for all the processor + architectures that are supported by Buildroot. + -
+The
package/directory contains the Makefiles and + associated files for all user-space tools and libraries that Buildroot + can compile and add to the target root filesystem. There is one + sub-directory per package. + -
+The
linux/directory contains the Makefiles and associated files for + the Linux kernel. + -
+The
boot/directory contains the Makefiles and associated files for + the bootloaders supported by Buildroot. + -
+The
system/directory contains support for system integration, e.g. + the target filesystem skeleton and the selection of an init system. + -
+The
fs/directory contains the Makefiles and + associated files for software related to the generation of the + target root filesystem image. +
Each directory contains at least 2 files:
-
+
something.mkis the Makefile that downloads, configures, + compiles and installs the packagesomething. + -
+
Config.inis a part of the configuration tool + description file. It describes the options related to the + package. +
The main Makefile performs the following steps (once the +configuration is done):
-
+Create all the output directories:
staging,target,build, + etc. in the output directory (output/by default, + another value can be specified usingO=) + - +Generate the toolchain target. When an internal toolchain is used, this + means generating the cross-compilation toolchain. When an external + toolchain is used, this means checking the features of the external + toolchain and importing it into the Buildroot environment. +
-
+Generate all the targets listed in the
TARGETSvariable. This + variable is filled by all the individual components' + Makefiles. Generating these targets will trigger the compilation of + the userspace packages (libraries, programs), the kernel, the + bootloader and the generation of the root filesystem images, + depending on the configuration. +
Overall, these coding style rules are here to help you to add new files in +Buildroot or refactor existing ones.
If you slightly modify some existing file, the important thing is +to keep the consistency of the whole file, so you can:
- +either follow the potentially deprecated coding style used in this +file, +
- +or entirely rework it in order to make it comply with these rules. +
Config.in files contain entries for almost anything configurable in
+Buildroot.
An entry has the following pattern:
config BR2_PACKAGE_LIBFOO + bool "libfoo" + depends on BR2_PACKAGE_LIBBAZ + select BR2_PACKAGE_LIBBAR + help + This is a comment that explains what libfoo is. + + http://foosoftware.org/libfoo/
-
+The
bool,depends on,selectandhelplines are indented + with one tab. + - +The help text itself should be indented with one tab and two + spaces. +
The Config.in files are the input for the configuration tool
+used in Buildroot, which is the regular Kconfig. For further
+details about the Kconfig language, refer to
+http://kernel.org/doc/Documentation/kbuild/kconfig-language.txt.
+Header: The file starts with a header. It contains the module name, +preferably in lowercase, enclosed between separators made of 80 hashes. A +blank line is mandatory after the header: +
################################################################################ +# +# libfoo +# +################################################################################
+Assignment: use
=preceded and followed by one space: +LIBFOO_VERSION = 1.0 +LIBFOO_CONF_OPTS += --without-python-support
Do not align the
=signs.+Indentation: use tab only: +
define LIBFOO_REMOVE_DOC + $(RM) -fr $(TARGET_DIR)/usr/share/libfoo/doc \ + $(TARGET_DIR)/usr/share/man/man3/libfoo* +endef
Note that commands inside a
defineblock should always start with a tab, +so make recognizes them as commands.+Optional dependency: +
+Prefer multi-line syntax. +
YES:
ifeq ($(BR2_PACKAGE_PYTHON),y) +LIBFOO_CONF_OPTS += --with-python-support +LIBFOO_DEPENDENCIES += python +else +LIBFOO_CONF_OPTS += --without-python-support +endif
NO:
LIBFOO_CONF_OPTS += --with$(if $(BR2_PACKAGE_PYTHON),,out)-python-support +LIBFOO_DEPENDENCIES += $(if $(BR2_PACKAGE_PYTHON),python,)
- +Keep configure options and dependencies close together. +
+Optional hooks: keep hook definition and assignment together in one + if block. +
YES:
ifneq ($(BR2_LIBFOO_INSTALL_DATA),y) +define LIBFOO_REMOVE_DATA + $(RM) -fr $(TARGET_DIR)/usr/share/libfoo/data +endef +LIBFOO_POST_INSTALL_TARGET_HOOKS += LIBFOO_REMOVE_DATA +endif
NO:
define LIBFOO_REMOVE_DATA + $(RM) -fr $(TARGET_DIR)/usr/share/libfoo/data +endef + +ifneq ($(BR2_LIBFOO_INSTALL_DATA),y) +LIBFOO_POST_INSTALL_TARGET_HOOKS += LIBFOO_REMOVE_DATA +endif
The documentation uses the +asciidoc format.
For further details about the asciidoc +syntax, refer to http://www.methods.co.nz/asciidoc/userguide.html.
Buildroot contains basic configurations for several publicly available +hardware boards, so that users of such a board can easily build a system +that is known to work. You are welcome to add support for other boards +to Buildroot too.
To do so, you need to create a normal Buildroot configuration that +builds a basic system for the hardware: toolchain, kernel, bootloader, +filesystem and a simple BusyBox-only userspace. No specific package +should be selected: the configuration should be as minimal as +possible, and should only build a working basic BusyBox system for the +target platform. You can of course use more complicated configurations +for your internal projects, but the Buildroot project will only +integrate basic board configurations. This is because package +selections are highly application-specific.
Once you have a known working configuration, run make
+savedefconfig. This will generate a minimal defconfig file at the
+root of the Buildroot source tree. Move this file into the configs/
+directory, and rename it <boardname>_defconfig.
It is recommended to use as much as possible upstream versions of the +Linux kernel and bootloaders, and to use as much as possible default +kernel and bootloader configurations. If they are incorrect for your +board, or no default exists, we encourage you to send fixes to the +corresponding upstream projects.
However, in the mean time, you may want to store kernel or bootloader
+configuration or patches specific to your target platform. To do so,
+create a directory board/<manufacturer> and a subdirectory
+board/<manufacturer>/<boardname>. You can then store your patches
+and configurations in these directories, and reference them from the main
+Buildroot configuration. Refer to Chapter 9, Project-specific customization for more details.
This section covers how new packages (userspace libraries or +applications) can be integrated into Buildroot. It also shows how +existing packages are integrated, which is needed for fixing issues or +tuning their configuration.
First of all, create a directory under the package directory for
+your software, for example libfoo.
Some packages have been grouped by topic in a sub-directory:
+x11r7, efl and matchbox. If your package fits in
+one of these categories, then create your package directory in these.
+New subdirectories are discouraged, however.
For the package to be displayed in the configuration tool, you need to
+create a Config file in your package directory. There are two types:
+Config.in and Config.in.host.
For packages used on the target, create a file named Config.in. This
+file will contain the option descriptions related to our libfoo software
+that will be used and displayed in the configuration tool. It should basically
+contain:
config BR2_PACKAGE_LIBFOO + bool "libfoo" + help + This is a comment that explains what libfoo is. + + http://foosoftware.org/libfoo/
The bool line, help line and other metadata information about the
+configuration option must be indented with one tab. The help text
+itself should be indented with one tab and two spaces, and it must
+mention the upstream URL of the project.
You can add other sub-options into a if
+BR2_PACKAGE_LIBFOOâ¦endif statement to configure particular things
+in your software. You can look at examples in other packages. The
+syntax of the Config.in file is the same as the one for the kernel
+Kconfig file. The documentation for this syntax is available at
+http://kernel.org/doc/Documentation/kbuild/kconfig-language.txt
Finally you have to add your new libfoo/Config.in to
+package/Config.in (or in a category subdirectory if you decided to
+put your package in one of the existing categories). The files
+included there are sorted alphabetically per category and are NOT
+supposed to contain anything but the bare name of the package.
source "package/libfoo/Config.in"
Some packages also need to be built for the host system. There are two +options here:
-
+The host package is only required to satisfy build-time
+ dependencies of one or more target packages. In this case, add
+
host-footo the target packageâsBAR_DEPENDENCIESvariable. No +Config.in.hostfile should be created. + +The host package should be explicitly selectable by the user from + the configuration menu. In this case, create a
Config.in.hostfile + for that host package: +config BR2_PACKAGE_HOST_FOO + bool "host foo" + help + This is a comment that explains what foo for the host is. + + http://foosoftware.org/foo/
The same coding style and options as for the
Config.infile are valid.Finally you have to add your new
libfoo/Config.in.hostto +package/Config.in.host. The files included there are sorted alphabetically +and are NOT supposed to contain anything but the bare name of the package.source "package/foo/Config.in.host"
The host package will then be available from the
Host utilitiesmenu.
The Config.in file of your package must also ensure that
+dependencies are enabled. Typically, Buildroot uses the following
+rules:
-
+Use a
selecttype of dependency for dependencies on + libraries. These dependencies are generally not obvious and it + therefore make sense to have the kconfig system ensure that the + dependencies are selected. For example, the libgtk2 package uses +select BR2_PACKAGE_LIBGLIB2to make sure this library is also + enabled. + Theselectkeyword expresses the dependency with a backward + semantic. + -
+Use a
depends ontype of dependency when the user really needs to + be aware of the dependency. Typically, Buildroot uses this type of + dependency for dependencies on target architecture, MMU support and + toolchain options (see Section 17.2.4, âDependencies on target and toolchain optionsâ), + or for dependencies on "big" things, such as the X.org system. + Thedepends onkeyword expresses the dependency with a forward + semantic. +
Note. The current problem with the kconfig language is that these two +dependency semantics are not internally linked. Therefore, it may be +possible to select a package, whom one of its dependencies/requirement +is not met.
An example illustrates both the usage of select and depends on.
config BR2_PACKAGE_RRDTOOL + bool "rrdtool" + depends on BR2_USE_WCHAR + select BR2_PACKAGE_FREETYPE + select BR2_PACKAGE_LIBART + select BR2_PACKAGE_LIBPNG + select BR2_PACKAGE_ZLIB + help + RRDtool is the OpenSource industry standard, high performance + data logging and graphing system for time series data. + + http://oss.oetiker.ch/rrdtool/ + +comment "rrdtool needs a toolchain w/ wchar" + depends on !BR2_USE_WCHAR
Note that these two dependency types are only transitive with the +dependencies of the same kind.
This means, in the following example:
config BR2_PACKAGE_A + bool "Package A" + +config BR2_PACKAGE_B + bool "Package B" + depends on BR2_PACKAGE_A + +config BR2_PACKAGE_C + bool "Package C" + depends on BR2_PACKAGE_B + +config BR2_PACKAGE_D + bool "Package D" + select BR2_PACKAGE_B + +config BR2_PACKAGE_E + bool "Package E" + select BR2_PACKAGE_D
-
+Selecting
Package Cwill be visible ifPackage Bhas been + selected, which in turn is only visible ifPackage Ahas been + selected. + -
+Selecting
Package Ewill selectPackage D, which will select +Package B, it will not check for the dependencies ofPackage B, + so it will not selectPackage A. + -
+Since
Package Bis selected butPackage Ais not, this violates + the dependency ofPackage BonPackage A. Therefore, in such a + situation, the transitive dependency has to be added explicitly: +
config BR2_PACKAGE_D + bool "Package D" + select BR2_PACKAGE_B + depends on BR2_PACKAGE_A + +config BR2_PACKAGE_E + bool "Package E" + select BR2_PACKAGE_D + depends on BR2_PACKAGE_A
Overall, for package library dependencies, select should be
+preferred.
Note that such dependencies will ensure that the dependency option
+is also enabled, but not necessarily built before your package. To do
+so, the dependency also needs to be expressed in the .mk file of the
+package.
Further formatting details: see the
+coding style
+Section 15.1, âConfig.in fileâ.
Many packages depend on certain options of the toolchain: the choice of +C library, C++ support, thread support, RPC support, wchar support, +or dynamic library support. Some packages can only be built on certain +target architectures, or if an MMU is available in the processor.
These dependencies have to be expressed with the appropriate depends
+on statements in the Config.in file. Additionally, for dependencies on
+toolchain options, a comment should be displayed when the option is
+not enabled, so that the user knows why the package is not available.
+Dependencies on target architecture or MMU support should not be
+made visible in a comment: since it is unlikely that the user can
+freely choose another target, it makes little sense to show these
+dependencies explicitly.
The comment should only be visible if the config option itself would
+be visible when the toolchain option dependencies are met. This means
+that all other dependencies of the package (including dependencies on
+target architecture and MMU support) have to be repeated on the
+comment definition. To keep it clear, the depends on statement for
+these non-toolchain option should be kept separate from the depends on
+statement for the toolchain options.
+If there is a dependency on a config option in that same file (typically
+the main package) it is preferable to have a global if ⦠endif
+construct rather than repeating the depends on statement on the
+comment and other config options.
The general format of a dependency comment for package foo is:
foo needs a toolchain w/ featA, featB, featC
for example:
mpd needs a toolchain w/ C++, threads, wchar
or
crda needs a toolchain w/ threads
Note that this text is kept brief on purpose, so that it will fit on a +80-character terminal.
The rest of this section enumerates the different target and toolchain +options, the corresponding config symbols to depend on, and the text to +use in the comment.
+Target architecture +
-
+Dependency symbol:
BR2_powerpc,BR2_mips, ⦠(seearch/Config.in) + - +Comment string: no comment to be added +
-
+Dependency symbol:
+MMU support +
-
+Dependency symbol:
BR2_USE_MMU+ - +Comment string: no comment to be added +
-
+Dependency symbol:
+Atomic instructions (whereby the architecture has instructions to + perform some operations atomically, like LOCKCMPXCHG on x86) +
-
+Dependency symbol:
BR2_ARCH_HAS_ATOMICS+ - +Comment string: no comment to be added +
-
+Dependency symbol:
+Kernel headers +
-
+Dependency symbol:
BR2_TOOLCHAIN_HEADERS_AT_LEAST_X_Y, (replace +X_Ywith the proper version, seetoolchain/toolchain-common.in) + -
+Comment string:
headers >= X.Yand/orheaders <= X.Y(replace +X.Ywith the proper version) +
-
+Dependency symbol:
+C library +
-
+Dependency symbol:
BR2_TOOLCHAIN_USES_GLIBC, +BR2_TOOLCHAIN_USES_MUSL,BR2_TOOLCHAIN_USES_UCLIBC+ -
+Comment string: for the C library, a slightly different comment text
+ is used:
foo needs an (e)glibc toolchain, orfoo needs an (e)glibc + toolchain w/ C+++
-
+Dependency symbol:
+C++ support +
-
+Dependency symbol:
BR2_INSTALL_LIBSTDCPP+ -
+Comment string:
C+++
-
+Dependency symbol:
+thread support +
-
+Dependency symbol:
BR2_TOOLCHAIN_HAS_THREADS+ -
+Comment string:
threads(unlessBR2_TOOLCHAIN_HAS_THREADS_NPTL+ is also needed, in which case, specifying onlyNPTLis sufficient) +
-
+Dependency symbol:
+NPTL thread support +
-
+Dependency symbol:
BR2_TOOLCHAIN_HAS_THREADS_NPTL+ -
+Comment string:
NPTL+
-
+Dependency symbol:
+RPC support +
-
+Dependency symbol:
BR2_TOOLCHAIN_HAS_NATIVE_RPC+ -
+Comment string:
RPC+
-
+Dependency symbol:
+wchar support +
-
+Dependency symbol:
BR2_USE_WCHAR+ -
+Comment string:
wchar+
-
+Dependency symbol:
+dynamic library +
-
+Dependency symbol:
!BR2_STATIC_LIBS+ -
+Comment string:
dynamic library+
-
+Dependency symbol:
Some packages need a Linux kernel to be built by buildroot. These are +typically kernel modules or firmware. A comment should be added in the +Config.in file to express this dependency, similar to dependencies on +toolchain options. The general format is:
foo needs a Linux kernel to be built
If there is a dependency on both toolchain options and the Linux +kernel, use this format:
foo needs a toolchain w/ featA, featB, featC and a Linux kernel to be built
If a package needs udev /dev management, it should depend on symbol
+BR2_PACKAGE_HAS_UDEV, and the following comment should be added:
foo needs udev /dev management
If there is a dependency on both toolchain options and udev /dev +management, use this format:
foo needs udev /dev management and a toolchain w/ featA, featB, featC
Some features can be provided by more than one package, such as the +openGL libraries.
See Section 17.11, âInfrastructure for virtual packagesâ for more on the virtual packages.
See Chapter 25, List of virtual packages for the symbols to depend on if your package +depends on a feature provided by a virtual package.
Finally, hereâs the hardest part. Create a file named libfoo.mk. It
+describes how the package should be downloaded, configured, built,
+installed, etc.
Depending on the package type, the .mk file must be written in a
+different way, using different infrastructures:
-
+Makefiles for generic packages (not using autotools or CMake):
+ These are based on an infrastructure similar to the one used for
+ autotools-based packages, but require a little more work from the
+ developer. They specify what should be done for the configuration,
+ compilation and installation of the package. This
+ infrastructure must be used for all packages that do not use the
+ autotools as their build system. In the future, other specialized
+ infrastructures might be written for other build systems. We cover
+ them through in a tutorial
+Section 17.5.1, â
generic-packagetutorialâ and a + reference +Section 17.5.2, âgeneric-packagereferenceâ. + -
+Makefiles for autotools-based software (autoconf, automake, etc.):
+ We provide a dedicated infrastructure for such packages, since
+ autotools is a very common build system. This infrastructure must
+ be used for new packages that rely on the autotools as their build
+ system. We cover them through a tutorial
+Section 17.6.1, â
autotools-packagetutorialâ + and reference +Section 17.6.2, âautotools-packagereferenceâ. + -
+Makefiles for cmake-based software: We provide a dedicated
+ infrastructure for such packages, as CMake is a more and more
+ commonly used build system and has a standardized behaviour. This
+ infrastructure must be used for new packages that rely on
+ CMake. We cover them through a tutorial
+Section 17.7.1, â
cmake-packagetutorialâ + and reference +Section 17.7.2, âcmake-packagereferenceâ. + -
+Makefiles for Python modules: We have a dedicated infrastructure
+ for Python modules that use either the
distutilsor the +setuptoolsmechanism. We cover them through a + tutorial +Section 17.8.1, âpython-packagetutorialâ and a + reference +Section 17.8.2, âpython-packagereferenceâ. + -
+Makefiles for Lua modules: We have a dedicated infrastructure for
+ Lua modules available through the LuaRocks web site. We cover them
+ through a tutorial
+Section 17.9.1, â
luarocks-packagetutorialâ and a + reference +Section 17.9.2, âluarocks-packagereferenceâ. +
Further formatting details: see the writing
+rules
+Section 15.2, âThe .mk fileâ.
Optionally, you can add a third file, named libfoo.hash, that contains
+the hashes of the downloaded files for the libfoo package.
The hashes stored in that file are used to validate the integrity of the +downloaded files.
The format of this file is one line for each file for which to check the +hash, each line being space-separated, with these three fields:
+the type of hash, one of: +
-
+
md5,sha1,sha224,sha256,sha384,sha512,none+
-
+
+the hash of the file: +
-
+for
none, one or more non-space chars, usually just the stringxxx+ -
+for
md5, 32 hexadecimal characters + -
+for
sha1, 40 hexadecimal characters + -
+for
sha224, 56 hexadecimal characters + -
+for
sha256, 64 hexadecimal characters + -
+for
sha384, 96 hexadecimal characters + -
+for
sha512, 128 hexadecimal characters +
-
+for
- +the name of the file, without any directory component +
Lines starting with a # sign are considered comments, and ignored. Empty
+lines are ignored.
There can be more than one hash for a single file, each on its own line. In +this case, all hashes must match.
Note. Ideally, the hashes stored in this file should match the hashes published by
+upstream, e.g. on their website, in the e-mail announcement⦠If upstream
+provides more than one type of hash (e.g. sha1 and sha512), then it is
+best to add all those hashes in the .hash file. If upstream does not
+provide any hash, or only provides an md5 hash, then compute at least one
+strong hash yourself (preferably sha256, but not md5), and mention
+this in a comment line above the hashes.
Note. If libfoo is from GitHub (see Section 17.17.2, âHow to add a package from GitHubâ for details), we
+can only accept a .hash file if the package is a released (e.g. uploaded
+by the maintainer) tarball. Otherwise, the automatically generated tarball
+may change over time, and thus its hashes may be different each time it is
+downloaded, causing a .hash mismatch for that tarball.
Note. The number of spaces does not matter, so one can use spaces (or tabs) to +properly align the different fields.
The none hash type is reserved to those archives downloaded from a
+repository, like a git clone, a subversion checkout⦠or archives
+downloaded with the github helper
+Section 17.17.2, âHow to add a package from GitHubâ.
The example below defines a sha1 and a sha256 published by upstream for
+the main libfoo-1.2.3.tar.bz2 tarball, an md5 from upstream and a
+locally-computed sha256 hashes for a binary blob, a sha256 for a
+downloaded patch, and an archive with no hash:
# Hashes from: http://www.foosoftware.org/download/libfoo-1.2.3.tar.bz2.{sha1,sha256}:
+sha1 486fb55c3efa71148fe07895fd713ea3a5ae343a libfoo-1.2.3.tar.bz2
+sha256 efc8103cc3bcb06bda6a781532d12701eb081ad83e8f90004b39ab81b65d4369 libfoo-1.2.3.tar.bz2
+
+# md5 from: http://www.foosoftware.org/download/libfoo-1.2.3.tar.bz2.md5, sha256 locally computed:
+md5 2d608f3c318c6b7557d551a5a09314f03452f1a1 libfoo-data.bin
+sha256 01ba4719c80b6fe911b091a7c05124b64eeece964e09c058ef8f9805daca546b libfoo-data.bin
+
+# Locally computed:
+sha256 ff52101fb90bbfc3fe9475e425688c660f46216d7e751c4bbdb1dc85cdccacb9 libfoo-fix-blabla.patch
+
+# No hash for 1234, comes from the github-helper:
+none xxx libfoo-1234.tar.gzIf the .hash file is present, and it contains one or more hashes for a
+downloaded file, the hash(es) computed by Buildroot (after download) must
+match the hash(es) stored in the .hash file. If one or more hashes do
+not match, Buildroot considers this an error, deletes the downloaded file,
+and aborts.
If the .hash file is present, but it does not contain a hash for a
+downloaded file, Buildroot considers this an error and aborts. However,
+the downloaded file is left in the download directory since this
+typically indicates that the .hash file is wrong but the downloaded
+file is probably OK.
Sources that are downloaded from a version control system (git, subversion, +etcâ¦) can not have a hash, because the version control system and tar +may not create exactly the same file (dates, files orderingâ¦), so the +hash could be wrong even for a valid download. Therefore, the hash check +is entirely skipped for such sources.
If the .hash file is missing, then no check is done at all.
By packages with specific build systems we mean all the packages +whose build system is not one of the standard ones, such as +autotools or CMake. This typically includes packages whose build +system is based on hand-written Makefiles or shell scripts.
01: ################################################################################ +02: # +03: # libfoo +04: # +05: ################################################################################ +06: +07: LIBFOO_VERSION = 1.0 +08: LIBFOO_SOURCE = libfoo-$(LIBFOO_VERSION).tar.gz +09: LIBFOO_SITE = http://www.foosoftware.org/download +10: LIBFOO_LICENSE = GPLv3+ +11: LIBFOO_LICENSE_FILES = COPYING +12: LIBFOO_INSTALL_STAGING = YES +13: LIBFOO_CONFIG_SCRIPTS = libfoo-config +14: LIBFOO_DEPENDENCIES = host-libaaa libbbb +15: +16: define LIBFOO_BUILD_CMDS +17: $(MAKE) CC="$(TARGET_CC)" LD="$(TARGET_LD)" -C $(@D) all +18: endef +19: +20: define LIBFOO_INSTALL_STAGING_CMDS +21: $(INSTALL) -D -m 0755 $(@D)/libfoo.a $(STAGING_DIR)/usr/lib/libfoo.a +22: $(INSTALL) -D -m 0644 $(@D)/foo.h $(STAGING_DIR)/usr/include/foo.h +23: $(INSTALL) -D -m 0755 $(@D)/libfoo.so* $(STAGING_DIR)/usr/lib +24: endef +25: +26: define LIBFOO_INSTALL_TARGET_CMDS +27: $(INSTALL) -D -m 0755 $(@D)/libfoo.so* $(TARGET_DIR)/usr/lib +28: $(INSTALL) -d -m 0755 $(TARGET_DIR)/etc/foo.d +29: endef +30: +31: define LIBFOO_DEVICES +32: /dev/foo c 666 0 0 42 0 - - - +33: endef +34: +35: define LIBFOO_PERMISSIONS +36: /bin/foo f 4755 0 0 - - - - - +37: endef +38: +39: define LIBFOO_USERS +40: foo -1 libfoo -1 * - - - LibFoo daemon +41: endef +42: +43: $(eval $(generic-package))
The Makefile begins on line 7 to 11 with metadata information: the
+version of the package (LIBFOO_VERSION), the name of the
+tarball containing the package (LIBFOO_SOURCE) (xz-ed tarball recommended)
+the Internet location at which the tarball can be downloaded from
+(LIBFOO_SITE), the license (LIBFOO_LICENSE) and file with the
+license text (LIBFOO_LICENSE_FILES). All variables must start with
+the same prefix, LIBFOO_ in this case. This prefix is always the
+uppercased version of the package name (see below to understand where
+the package name is defined).
On line 12, we specify that this package wants to install something to
+the staging space. This is often needed for libraries, since they must
+install header files and other development files in the staging space.
+This will ensure that the commands listed in the
+LIBFOO_INSTALL_STAGING_CMDS variable will be executed.
On line 13, we specify that there is some fixing to be done to some
+of the libfoo-config files that were installed during
+LIBFOO_INSTALL_STAGING_CMDS phase.
+These *-config files are executable shell script files that are
+located in $(STAGING_DIR)/usr/bin directory and are executed
+by other 3rd party packages to find out the location and the linking
+flags of this particular package.
The problem is that all these *-config files by default give wrong, +host system linking flags that are unsuitable for cross-compiling.
For example: -I/usr/include instead of -I$(STAGING_DIR)/usr/include +or: -L/usr/lib instead of -L$(STAGING_DIR)/usr/lib
So some sed magic is done to these scripts to make them give correct
+flags.
+The argument to be given to LIBFOO_CONFIG_SCRIPTS is the file name(s)
+of the shell script(s) needing fixing. All these names are relative to
+$(STAGING_DIR)/usr/bin and if needed multiple names can be given.
In addition, the scripts listed in LIBFOO_CONFIG_SCRIPTS are removed
+from $(TARGET_DIR)/usr/bin, since they are not needed on the target.
Example 17.1. Config script: divine package
Package divine installs shell script $(STAGING_DIR)/usr/bin/divine-config.
So its fixup would be:
DIVINE_CONFIG_SCRIPTS = divine-config
Example 17.2. Config script: imagemagick package:
Package imagemagick installs the following scripts: +$(STAGING_DIR)/usr/bin/{Magick,Magick++,MagickCore,MagickWand,Wand}-config
So itâs fixup would be:
IMAGEMAGICK_CONFIG_SCRIPTS = \ + Magick-config Magick++-config \ + MagickCore-config MagickWand-config Wand-config
On line 14, we specify the list of dependencies this package relies
+on. These dependencies are listed in terms of lower-case package names,
+which can be packages for the target (without the host-
+prefix) or packages for the host (with the host-) prefix).
+Buildroot will ensure that all these packages are built and installed
+before the current package starts its configuration.
The rest of the Makefile, lines 16..29, defines what should be done
+at the different steps of the package configuration, compilation and
+installation.
+LIBFOO_BUILD_CMDS tells what steps should be performed to
+build the package. LIBFOO_INSTALL_STAGING_CMDS tells what
+steps should be performed to install the package in the staging space.
+LIBFOO_INSTALL_TARGET_CMDS tells what steps should be
+performed to install the package in the target space.
All these steps rely on the $(@D) variable, which
+contains the directory where the source code of the package has been
+extracted.
On line 31..33, we define a device-node file used by this package
+(LIBFOO_DEVICES).
On line 35..37, we define the permissions to set to specific files
+installed by this package (LIBFOO_PERMISSIONS).
On lines 39..41, we define a user that is used by this package (e.g.
+to run a daemon as non-root) (LIBFOO_USERS).
Finally, on line 43, we call the generic-package function, which
+generates, according to the variables defined previously, all the
+Makefile code necessary to make your package working.
There are two variants of the generic target. The generic-package macro is
+used for packages to be cross-compiled for the target. The
+host-generic-package macro is used for host packages, natively compiled
+for the host. It is possible to call both of them in a single .mk
+file: once to create the rules to generate a target
+package and once to create the rules to generate a host package:
$(eval $(generic-package)) +$(eval $(host-generic-package))
This might be useful if the compilation of the target package requires
+some tools to be installed on the host. If the package name is
+libfoo, then the name of the package for the target is also
+libfoo, while the name of the package for the host is
+host-libfoo. These names should be used in the DEPENDENCIES
+variables of other packages, if they depend on libfoo or
+host-libfoo.
The call to the generic-package and/or host-generic-package macro must be
+at the end of the .mk file, after all variable definitions.
For the target package, the generic-package uses the variables defined by
+the .mk file and prefixed by the uppercased package name:
+LIBFOO_*. host-generic-package uses the HOST_LIBFOO_* variables. For
+some variables, if the HOST_LIBFOO_ prefixed variable doesnât
+exist, the package infrastructure uses the corresponding variable
+prefixed by LIBFOO_. This is done for variables that are likely to
+have the same value for both the target and host packages. See below
+for details.
The list of variables that can be set in a .mk file to give metadata
+information is (assuming the package name is libfoo) :
-
+
LIBFOO_VERSION, mandatory, must contain the version of the + package. Note that ifHOST_LIBFOO_VERSIONdoesnât exist, it is + assumed to be the same asLIBFOO_VERSION. It can also be a + revision number, branch or tag for packages that are fetched + directly from their revision control system. + Examples: +LIBFOO_VERSION = 0.1.2+LIBFOO_VERSION = cb9d6aa9429e838f0e54faa3d455bcbab5eef057+LIBFOO_VERSION = stable+ -
+
LIBFOO_SOURCEmay contain the name of the tarball of the package, + which Buildroot will use to download the tarball from +LIBFOO_SITE. IfHOST_LIBFOO_SOURCEis not specified, it defaults + toLIBFOO_SOURCE. If none are specified, then the value is assumed + to belibfoo-$(LIBFOO_VERSION).tar.gz. + Example:LIBFOO_SOURCE = foobar-$(LIBFOO_VERSION).tar.bz2+ -
+
LIBFOO_PATCHmay contain a space-separated list of patch file + names, that Buildroot will download and apply to the package source + code. If an entry contains://, then Buildroot will assume it is a + full URL and download the patch from this location. Otherwise, + Buildroot will assume that the patch should be downloaded from +LIBFOO_SITE. IfHOST_LIBFOO_PATCHis not specified, it defaults + toLIBFOO_PATCH. Note that patches that are included in Buildroot + itself use a different mechanism: all files of the form +*.patchpresent in the package directory inside + Buildroot will be applied to the package after extraction (see + patching a package +Chapter 18, Patching a package). Finally, patches listed in + theLIBFOO_PATCHvariable are applied before the patches stored + in the Buildroot package directory. + -
+
LIBFOO_SITEprovides the location of the package, which can be a + URL or a local filesystem path. HTTP, FTP and SCP are supported URL + types for retrieving package tarballs. Git, Subversion, Mercurial, + and Bazaar are supported URL types for retrieving packages directly + from source code management systems. There is a helper function to make + it easier to download source tarballs from GitHub (refer to + Section 17.17.2, âHow to add a package from GitHubâ for details). A filesystem path may be used + to specify either a tarball or a directory containing the package + source code. SeeLIBFOO_SITE_METHODbelow for more details on how + retrieval works. + Note that SCP URLs should be of the form +scp://[user@]host:filepath, and that filepath is relative to the + userâs home directory, so you may want to prepend the path with a + slash for absolute paths: +scp://[user@]host:/absolutepath. + IfHOST_LIBFOO_SITEis not specified, it defaults to +LIBFOO_SITE. + Examples: +LIBFOO_SITE=http://www.libfoosoftware.org/libfoo+LIBFOO_SITE=http://svn.xiph.org/trunk/Tremor+LIBFOO_SITE=/opt/software/libfoo.tar.gz+LIBFOO_SITE=$(TOPDIR)/../src/libfoo/+ -
+
LIBFOO_EXTRA_DOWNLOADSis a space-separated list of additional + files that Buildroot should download. If an entry contains://+ then Buildroot will assume it is a complete URL and will download + the file using this URL. Otherwise, Buildroot will assume the file + to be downloaded is located atLIBFOO_SITE. Buildroot will not do + anything with those additional files, except download them: it will + be up to the package recipe to use them from$(BR2_DL_DIR). + +
LIBFOO_SITE_METHODdetermines the method used to fetch or copy the + package source code. In many cases, Buildroot guesses the method + from the contents ofLIBFOO_SITEand settingLIBFOO_SITE_METHOD+ is unnecessary. WhenHOST_LIBFOO_SITE_METHODis not specified, it + defaults to the value ofLIBFOO_SITE_METHOD. + The possible values ofLIBFOO_SITE_METHODare: +-
+
wgetfor normal FTP/HTTP downloads of tarballs. Used by + default whenLIBFOO_SITEbegins withhttp://,https://or +ftp://. + -
+
scpfor downloads of tarballs over SSH with scp. Used by + default whenLIBFOO_SITEbegins withscp://. + -
+
svnfor retrieving source code from a Subversion repository. + Used by default whenLIBFOO_SITEbegins withsvn://. When a +http://Subversion repository URL is specified in +LIBFOO_SITE, one must specifyLIBFOO_SITE_METHOD=svn. + Buildroot performs a checkout which is preserved as a tarball in + the download cache; subsequent builds use the tarball instead of + performing another checkout. + -
+
cvsfor retrieving source code from a CVS repository. + Used by default whenLIBFOO_SITEbegins withcvs://. + The downloaded source code is cached as with thesvnmethod. + Only anonymous pserver mode is supported. +LIBFOO_SITEmust contain the source URL as well as the remote + repository directory. The module is the package name. +LIBFOO_VERSIONis mandatory and must be a timestamp. + -
+
gitfor retrieving source code from a Git repository. Used by + default whenLIBFOO_SITEbegins withgit://. The downloaded + source code is cached as with thesvn+ method. + -
+
hgfor retrieving source code from a Mercurial repository. One + must specifyLIBFOO_SITE_METHOD=hgwhenLIBFOO_SITE+ contains a Mercurial repository URL. The downloaded source code + is cached as with thesvnmethod. + -
+
bzrfor retrieving source code from a Bazaar repository. Used + by default whenLIBFOO_SITEbegins withbzr://. The + downloaded source code is cached as with thesvnmethod. + -
+
filefor a local tarball. One should use this when +LIBFOO_SITEspecifies a package tarball as a local filename. + Useful for software that isnât available publicly or in version + control. + -
+
localfor a local source code directory. One should use this + whenLIBFOO_SITEspecifies a local directory path containing + the package source code. Buildroot copies the contents of the + source directory into the packageâs build directory. +
-
+
-
+
LIBFOO_DEPENDENCIESlists the dependencies (in terms of package + name) that are required for the current target package to + compile. These dependencies are guaranteed to be compiled and + installed before the configuration of the current package starts. In + a similar way,HOST_LIBFOO_DEPENDENCIESlists the dependencies for + the current host package. + -
+
LIBFOO_PATCH_DEPENDENCIESlists the dependencies (in terms of + package name) that are required for the current package to be + patched. These dependencies are guaranteed to be extracted and + patched before the current package is patched. In a similar way, +HOST_LIBFOO_PATCH_DEPENDENCIESlists the dependencies for the + current host package. + This is seldom used; usually,LIBFOO_DEPENDENCIESis what you + really want to use. + -
+
LIBFOO_PROVIDESlists all the virtual packageslibfoois an + implementation of. See Section 17.11, âInfrastructure for virtual packagesâ. + -
+
LIBFOO_INSTALL_STAGINGcan be set toYESorNO(default). If + set toYES, then the commands in theLIBFOO_INSTALL_STAGING_CMDS+ variables are executed to install the package into the staging + directory. + -
+
LIBFOO_INSTALL_TARGETcan be set toYES(default) orNO. If + set toYES, then the commands in theLIBFOO_INSTALL_TARGET_CMDS+ variables are executed to install the package into the target + directory. + -
+
LIBFOO_INSTALL_IMAGEScan be set toYESorNO(default). If + set toYES, then the commands in theLIBFOO_INSTALL_IMAGES_CMDS+ variable are executed to install the package into the images + directory. + -
+
LIBFOO_CONFIG_SCRIPTSlists the names of the files in + $(STAGING_DIR)/usr/bin that need some special fixing to make them + cross-compiling friendly. Multiple file names separated by space can + be given and all are relative to $(STAGING_DIR)/usr/bin. The files + listed inLIBFOO_CONFIG_SCRIPTSare also removed from +$(TARGET_DIR)/usr/binsince they are not needed on the target. + -
+
LIBFOO_DEVICESlists the device files to be created by Buildroot + when using the static device table. The syntax to use is the + makedevs one. You can find some documentation for this syntax in the + Chapter 22, Makedev syntax documentation. This variable is optional. + -
+
LIBFOO_PERMISSIONSlists the changes of permissions to be done at + the end of the build process. The syntax is once again the makedevs one. + You can find some documentation for this syntax in the Chapter 22, Makedev syntax documentation. + This variable is optional. + -
+
LIBFOO_USERSlists the users to create for this package, if it installs + a program you want to run as a specific user (e.g. as a daemon, or as a + cron-job). The syntax is similar in spirit to the makedevs one, and is + described in the Chapter 23, Makeusers syntax documentation. This variable is optional. + -
+
LIBFOO_LICENSEdefines the license (or licenses) under which the package + is released. + This name will appear in the manifest file produced bymake legal-info. + If the license appears in the following list +Section 12.2, âLicense abbreviationsâ, + use the same string to make the manifest file uniform. + Otherwise, describe the license in a precise and concise way, avoiding + ambiguous names such asBSDwhich actually name a family of licenses. + This variable is optional. If it is not defined,unknownwill appear in + thelicensefield of the manifest file for this package. + -
+
LIBFOO_LICENSE_FILESis a space-separated list of files in the package + tarball that contain the license(s) under which the package is released. +make legal-infocopies all of these files in thelegal-infodirectory. + See Chapter 12, Legal notice and licensing for more information. + This variable is optional. If it is not defined, a warning will be produced + to let you know, andnot savedwill appear in thelicense filesfield + of the manifest file for this package. + -
+
LIBFOO_REDISTRIBUTEcan be set toYES(default) orNOto indicate if + the package source code is allowed to be redistributed. Set it toNOfor + non-opensource packages: Buildroot will not save the source code for this + package when collecting thelegal-info. + -
+
LIBFOO_FLAT_STACKSIZEdefines the stack size of an application built into + the FLAT binary format. The application stack size on the NOMMU architecture + processors canât be enlarged at run time. The default stack size for the + FLAT binary format is only 4k bytes. If the application consumes more stack, + append the required number here. +
The recommended way to define these variables is to use the following +syntax:
LIBFOO_VERSION = 2.32
Now, the variables that define what should be performed at the +different steps of the build process.
-
+
LIBFOO_EXTRACT_CMDSlists the actions to be performed to extract + the package. This is generally not needed as tarballs are + automatically handled by Buildroot. However, if the package uses a + non-standard archive format, such as a ZIP or RAR file, or has a + tarball with a non-standard organization, this variable allows to + override the package infrastructure default behavior. + -
+
LIBFOO_CONFIGURE_CMDSlists the actions to be performed to + configure the package before its compilation. + -
+
LIBFOO_BUILD_CMDSlists the actions to be performed to + compile the package. + -
+
HOST_LIBFOO_INSTALL_CMDSlists the actions to be performed + to install the package, when the package is a host package. The + package must install its files to the directory given by +$(HOST_DIR). All files, including development files such as + headers should be installed, since other packages might be compiled + on top of this package. + -
+
LIBFOO_INSTALL_TARGET_CMDSlists the actions to be + performed to install the package to the target directory, when the + package is a target package. The package must install its files to + the directory given by$(TARGET_DIR). Only the files required for + execution of the package have to be + installed. Header files, static libraries and documentation will be + removed again when the target filesystem is finalized. + -
+
LIBFOO_INSTALL_STAGING_CMDSlists the actions to be + performed to install the package to the staging directory, when the + package is a target package. The package must install its files to + the directory given by$(STAGING_DIR). All development files + should be installed, since they might be needed to compile other + packages. + -
+
LIBFOO_INSTALL_IMAGES_CMDSlists the actions to be performed to + install the package to the images directory, when the package is a + target package. The package must install its files to the directory + given by$(BINARIES_DIR). Only files that are binary images (aka + images) that do not belong in theTARGET_DIRbut are necessary + for booting the board should be placed here. For example, a package + should utilize this step if it has binaries which would be similar + to the kernel image, bootloader or root filesystem images. + -
+
LIBFOO_INSTALL_INIT_SYSVandLIBFOO_INSTALL_INIT_SYSTEMDlist the + actions to install init scripts either for the systemV-like init systems + (busybox, sysvinit, etc.) or for the systemd units. These commands + will be run only when the relevant init system is installed (i.e. if + systemd is selected as the init system in the configuration, only +LIBFOO_INSTALL_INIT_SYSTEMDwill be run). +
The preferred way to define these variables is:
define LIBFOO_CONFIGURE_CMDS + action 1 + action 2 + action 3 +endef
In the action definitions, you can use the following variables:
-
+
$(@D), which contains the directory in which the package source + code has been uncompressed. + -
+
$(TARGET_CC),$(TARGET_LD), etc. to get the target + cross-compilation utilities + -
+
$(TARGET_CROSS)to get the cross-compilation toolchain prefix + -
+Of course the
$(HOST_DIR),$(STAGING_DIR)and$(TARGET_DIR)+ variables to install the packages properly. +
Finally, you can also use hooks. See Section 17.15, âHooks available in the various build stepsâ for more information.
First, letâs see how to write a .mk file for an autotools-based
+package, with an example :
01: ################################################################################ +02: # +03: # libfoo +04: # +05: ################################################################################ +06: +07: LIBFOO_VERSION = 1.0 +08: LIBFOO_SOURCE = libfoo-$(LIBFOO_VERSION).tar.gz +09: LIBFOO_SITE = http://www.foosoftware.org/download +10: LIBFOO_INSTALL_STAGING = YES +11: LIBFOO_INSTALL_TARGET = NO +12: LIBFOO_CONF_OPTS = --disable-shared +13: LIBFOO_DEPENDENCIES = libglib2 host-pkgconf +14: +15: $(eval $(autotools-package))
On line 7, we declare the version of the package.
On line 8 and 9, we declare the name of the tarball (xz-ed tarball recommended) +and the location of the tarball on the Web. Buildroot will automatically +download the tarball from this location.
On line 10, we tell Buildroot to install the package to the staging
+directory. The staging directory, located in output/staging/
+is the directory where all the packages are installed, including their
+development files, etc. By default, packages are not installed to the
+staging directory, since usually, only libraries need to be installed in
+the staging directory: their development files are needed to compile
+other libraries or applications depending on them. Also by default, when
+staging installation is enabled, packages are installed in this location
+using the make install command.
On line 11, we tell Buildroot to not install the package to the
+target directory. This directory contains what will become the root
+filesystem running on the target. For purely static libraries, it is
+not necessary to install them in the target directory because they will
+not be used at runtime. By default, target installation is enabled; setting
+this variable to NO is almost never needed. Also by default, packages are
+installed in this location using the make install command.
On line 12, we tell Buildroot to pass a custom configure option, that
+will be passed to the ./configure script before configuring
+and building the package.
On line 13, we declare our dependencies, so that they are built +before the build process of our package starts.
Finally, on line line 15, we invoke the autotools-package
+macro that generates all the Makefile rules that actually allows the
+package to be built.
The main macro of the autotools package infrastructure is
+autotools-package. It is similar to the generic-package macro. The ability to
+have target and host packages is also available, with the
+host-autotools-package macro.
Just like the generic infrastructure, the autotools infrastructure
+works by defining a number of variables before calling the
+autotools-package macro.
First, all the package metadata information variables that exist in the
+generic infrastructure also exist in the autotools infrastructure:
+LIBFOO_VERSION, LIBFOO_SOURCE,
+LIBFOO_PATCH, LIBFOO_SITE,
+LIBFOO_SUBDIR, LIBFOO_DEPENDENCIES,
+LIBFOO_INSTALL_STAGING, LIBFOO_INSTALL_TARGET.
A few additional variables, specific to the autotools infrastructure, +can also be defined. Many of them are only useful in very specific +cases, typical packages will therefore only use a few of them.
-
+
LIBFOO_SUBDIRmay contain the name of a subdirectory + inside the package that contains the configure script. This is useful, + if for example, the main configure script is not at the root of the + tree extracted by the tarball. IfHOST_LIBFOO_SUBDIRis + not specified, it defaults toLIBFOO_SUBDIR. + -
+
LIBFOO_CONF_ENV, to specify additional environment + variables to pass to the configure script. By default, empty. + -
+
LIBFOO_CONF_OPTS, to specify additional configure + options to pass to the configure script. By default, empty. + -
+
LIBFOO_MAKE, to specify an alternatemake+ command. This is typically useful when parallel make is enabled in + the configuration (usingBR2_JLEVEL) but that this + feature should be disabled for the given package, for one reason or + another. By default, set to$(MAKE). If parallel building + is not supported by the package, then it should be set to +LIBFOO_MAKE=$(MAKE1). + -
+
LIBFOO_MAKE_ENV, to specify additional environment + variables to pass to make in the build step. These are passed before + themakecommand. By default, empty. + -
+
LIBFOO_MAKE_OPTS, to specify additional variables to + pass to make in the build step. These are passed after the +makecommand. By default, empty. + -
+
LIBFOO_AUTORECONF, tells whether the package should + be autoreconfigured or not (i.e. if the configure script and + Makefile.in files should be re-generated by re-running autoconf, + automake, libtool, etc.). Valid values areYESand +NO. By default, the value isNO+ -
+
LIBFOO_AUTORECONF_ENV, to specify additional environment + variables to pass to the autoreconf program if +LIBFOO_AUTORECONF=YES. These are passed in the environment of + the autoreconf command. By default, empty. + -
+
LIBFOO_AUTORECONF_OPTSto specify additional options + passed to the autoreconf program if +LIBFOO_AUTORECONF=YES. By default, empty. + -
+
LIBFOO_GETTEXTIZE, tells whether the package should be + gettextized or not (i.e. if the package uses a different gettext + version than Buildroot provides, and it is needed to run + gettextize.) Only valid whenLIBFOO_AUTORECONF=YES. Valid + values areYESandNO. The default isNO. + -
+
LIBFOO_GETTEXTIZE_OPTS, to specify additional options passed to + the gettextize program, ifLIBFOO_GETTEXTIZE=YES. You may + use that if, for example, the.pofiles are not located in the + standard place (i.e. inpo/at the root of the package.) By + default, -f. + -
+
LIBFOO_LIBTOOL_PATCHtells whether the Buildroot + patch to fix libtool cross-compilation issues should be applied or + not. Valid values areYESandNO. By + default, the value isYES+ -
+
LIBFOO_INSTALL_STAGING_OPTScontains the make options + used to install the package to the staging directory. By default, the + value isDESTDIR=$(STAGING_DIR) install, which is + correct for most autotools packages. It is still possible to override + it. + -
+
LIBFOO_INSTALL_TARGET_OPTScontains the make options + used to install the package to the target directory. By default, the + value isDESTDIR=$(TARGET_DIR) install. The default + value is correct for most autotools packages, but it is still possible + to override it if needed. +
With the autotools infrastructure, all the steps required to build +and install the packages are already defined, and they generally work +well for most autotools-based packages. However, when required, it is +still possible to customize what is done in any particular step:
- +By adding a post-operation hook (after extract, patch, configure, + build or install). See Section 17.15, âHooks available in the various build stepsâ for details. +
-
+By overriding one of the steps. For example, even if the autotools
+ infrastructure is used, if the package
.mkfile defines its + ownLIBFOO_CONFIGURE_CMDSvariable, it will be used + instead of the default autotools one. However, using this method + should be restricted to very specific cases. Do not use it in the + general case. +
First, letâs see how to write a .mk file for a CMake-based package,
+with an example :
01: ################################################################################ +02: # +03: # libfoo +04: # +05: ################################################################################ +06: +07: LIBFOO_VERSION = 1.0 +08: LIBFOO_SOURCE = libfoo-$(LIBFOO_VERSION).tar.gz +09: LIBFOO_SITE = http://www.foosoftware.org/download +10: LIBFOO_INSTALL_STAGING = YES +11: LIBFOO_INSTALL_TARGET = NO +12: LIBFOO_CONF_OPTS = -DBUILD_DEMOS=ON +13: LIBFOO_DEPENDENCIES = libglib2 host-pkgconf +14: +15: $(eval $(cmake-package))
On line 7, we declare the version of the package.
On line 8 and 9, we declare the name of the tarball (xz-ed tarball recommended) +and the location of the tarball on the Web. Buildroot will automatically +download the tarball from this location.
On line 10, we tell Buildroot to install the package to the staging
+directory. The staging directory, located in output/staging/
+is the directory where all the packages are installed, including their
+development files, etc. By default, packages are not installed to the
+staging directory, since usually, only libraries need to be installed in
+the staging directory: their development files are needed to compile
+other libraries or applications depending on them. Also by default, when
+staging installation is enabled, packages are installed in this location
+using the make install command.
On line 11, we tell Buildroot to not install the package to the
+target directory. This directory contains what will become the root
+filesystem running on the target. For purely static libraries, it is
+not necessary to install them in the target directory because they will
+not be used at runtime. By default, target installation is enabled; setting
+this variable to NO is almost never needed. Also by default, packages are
+installed in this location using the make install command.
On line 12, we tell Buildroot to pass custom options to CMake when it is +configuring the package.
On line 13, we declare our dependencies, so that they are built +before the build process of our package starts.
Finally, on line line 15, we invoke the cmake-package
+macro that generates all the Makefile rules that actually allows the
+package to be built.
The main macro of the CMake package infrastructure is
+cmake-package. It is similar to the generic-package macro. The ability to
+have target and host packages is also available, with the
+host-cmake-package macro.
Just like the generic infrastructure, the CMake infrastructure works
+by defining a number of variables before calling the cmake-package
+macro.
First, all the package metadata information variables that exist in
+the generic infrastructure also exist in the CMake infrastructure:
+LIBFOO_VERSION, LIBFOO_SOURCE, LIBFOO_PATCH, LIBFOO_SITE,
+LIBFOO_SUBDIR, LIBFOO_DEPENDENCIES, LIBFOO_INSTALL_STAGING,
+LIBFOO_INSTALL_TARGET.
A few additional variables, specific to the CMake infrastructure, can +also be defined. Many of them are only useful in very specific cases, +typical packages will therefore only use a few of them.
-
+
LIBFOO_SUBDIRmay contain the name of a subdirectory inside the + package that contains the main CMakeLists.txt file. This is useful, + if for example, the main CMakeLists.txt file is not at the root of + the tree extracted by the tarball. IfHOST_LIBFOO_SUBDIRis not + specified, it defaults toLIBFOO_SUBDIR. + -
+
LIBFOO_CONF_ENV, to specify additional environment variables to + pass to CMake. By default, empty. + +
LIBFOO_CONF_OPTS, to specify additional configure options to pass + to CMake. By default, empty. A number of common CMake options are + set by thecmake-packageinfrastructure; so it is normally not + necessary to set them in the packageâs*.mkfile unless you want + to override them: +-
+
CMAKE_BUILD_TYPEis driven byBR2_ENABLE_DEBUG; + -
+
CMAKE_INSTALL_PREFIX; + -
+
BUILD_SHARED_LIBSis driven byBR2_STATIC_LIBS; + -
+
BUILD_DOC,BUILD_DOCSare disabled; + -
+
BUILD_EXAMPLE,BUILD_EXAMPLESare disabled; + -
+
BUILD_TEST,BUILD_TESTS,BUILD_TESTINGare disabled. +
-
+
-
+
LIBFOO_SUPPORTS_IN_SOURCE_BUILD = NOshould be set when the package + cannot be built inside the source tree but needs a separate build + directory. + -
+
LIBFOO_MAKE, to specify an alternatemakecommand. This is + typically useful when parallel make is enabled in the configuration + (usingBR2_JLEVEL) but that this feature should be disabled for + the given package, for one reason or another. By default, set to +$(MAKE). If parallel building is not supported by the package, + then it should be set toLIBFOO_MAKE=$(MAKE1). + -
+
LIBFOO_MAKE_ENV, to specify additional environment variables to + pass to make in the build step. These are passed before themake+ command. By default, empty. + -
+
LIBFOO_MAKE_OPTS, to specify additional variables to pass to make + in the build step. These are passed after themakecommand. By + default, empty. + -
+
LIBFOO_INSTALL_STAGING_OPTScontains the make options used to + install the package to the staging directory. By default, the value + isDESTDIR=$(STAGING_DIR) install, which is correct for most + CMake packages. It is still possible to override it. + -
+
LIBFOO_INSTALL_TARGET_OPTScontains the make options used to + install the package to the target directory. By default, the value + isDESTDIR=$(TARGET_DIR) install. The default value is correct + for most CMake packages, but it is still possible to override it if + needed. +
With the CMake infrastructure, all the steps required to build and +install the packages are already defined, and they generally work well +for most CMake-based packages. However, when required, it is still +possible to customize what is done in any particular step:
- +By adding a post-operation hook (after extract, patch, configure, + build or install). See Section 17.15, âHooks available in the various build stepsâ for details. +
-
+By overriding one of the steps. For example, even if the CMake
+ infrastructure is used, if the package
.mkfile defines its own +LIBFOO_CONFIGURE_CMDSvariable, it will be used instead of the + default CMake one. However, using this method should be restricted + to very specific cases. Do not use it in the general case. +
This infrastructure applies to Python packages that use the standard
+Python setuptools mechanism as their build system, generally
+recognizable by the usage of a setup.py script.
First, letâs see how to write a .mk file for a Python package,
+with an example :
01: ################################################################################ +02: # +03: # python-foo +04: # +05: ################################################################################ +06: +07: PYTHON_FOO_VERSION = 1.0 +08: PYTHON_FOO_SOURCE = python-foo-$(PYTHON_FOO_VERSION).tar.xz +09: PYTHON_FOO_SITE = http://www.foosoftware.org/download +10: PYTHON_FOO_LICENSE = BSD-3c +11: PYTHON_FOO_LICENSE_FILES = LICENSE +12: PYTHON_FOO_ENV = SOME_VAR=1 +13: PYTHON_FOO_DEPENDENCIES = libmad +14: PYTHON_FOO_SETUP_TYPE = distutils +15: +16: $(eval $(python-package))
On line 7, we declare the version of the package.
On line 8 and 9, we declare the name of the tarball (xz-ed tarball +recommended) and the location of the tarball on the Web. Buildroot +will automatically download the tarball from this location.
On line 10 and 11, we give licensing details about the package (its +license on line 10, and the file containing the license text on line +11).
On line 12, we tell Buildroot to pass custom options to the Python
+setup.py script when it is configuring the package.
On line 13, we declare our dependencies, so that they are built +before the build process of our package starts.
On line 14, we declare the specific Python build system being used. In
+this case the distutils Python build system is used. The two
+supported ones are distutils and setuptools.
Finally, on line 16, we invoke the python-package macro that
+generates all the Makefile rules that actually allow the package to be
+built.
As a policy, packages that merely provide Python modules should all be
+named python-<something> in Buildroot. Other packages that use the
+Python build system, but are not Python modules, can freely choose
+their name (existing examples in Buildroot are scons and
+supervisor).
In their Config.in file, they should depend on BR2_PACKAGE_PYTHON
+so that when Buildroot will enable Python 3 usage for modules, we will
+be able to enable Python modules progressively on Python 3.
The main macro of the Python package infrastructure is
+python-package. It is similar to the generic-package macro. It is
+also possible to create Python host packages with the
+host-python-package macro.
Just like the generic infrastructure, the Python infrastructure works
+by defining a number of variables before calling the python-package
+or host-python-package macros.
All the package metadata information variables that exist in the
+generic package infrastructure
+Section 17.5.2, âgeneric-package referenceâ also
+exist in the Python infrastructure: PYTHON_FOO_VERSION,
+PYTHON_FOO_SOURCE, PYTHON_FOO_PATCH, PYTHON_FOO_SITE,
+PYTHON_FOO_SUBDIR, PYTHON_FOO_DEPENDENCIES, PYTHON_FOO_LICENSE,
+PYTHON_FOO_LICENSE_FILES, PYTHON_FOO_INSTALL_STAGING, etc.
Note that:
-
+It is not necessary to add
pythonorhost-pythonin the +PYTHON_FOO_DEPENDENCIESvariable of a package, since these basic + dependencies are automatically added as needed by the Python + package infrastructure. + -
+Similarly, it is not needed to add
host-setuptoolsand/or +host-distutilscrossdependencies toPYTHON_FOO_DEPENDENCIESfor + setuptools-based packages, since these are automatically added by + the Python infrastructure as needed. +
One variable specific to the Python infrastructure is mandatory:
-
+
PYTHON_FOO_SETUP_TYPE, to define which Python build system is used + by the package. The two supported values aredistutilsand +setuptools. If you donât know which one is used in your package, + look at thesetup.pyfile in your package source code, and see + whether it imports things from thedistutilsmodule or the +setuptoolsmodule. +
A few additional variables, specific to the Python infrastructure, can +optionally be defined, depending on the packageâs needs. Many of them +are only useful in very specific cases, typical packages will +therefore only use a few of them, or none.
-
+
PYTHON_FOO_ENV, to specify additional environment variables to + pass to the Pythonsetup.pyscript (for both the build and install + steps). Note that the infrastructure is automatically passing + several standard variables, defined inPKG_PYTHON_DISTUTILS_ENV+ (for distutils target packages),HOST_PKG_PYTHON_DISTUTILS_ENV+ (for distutils host packages),PKG_PYTHON_SETUPTOOLS_ENV(for + setuptools target packages) andHOST_PKG_PYTHON_SETUPTOOLS_ENV+ (for setuptools host packages). + -
+
PYTHON_FOO_BUILD_OPTS, to specify additional options to pass to the + Pythonsetup.pyscript during the build step. For target distutils + packages, thePKG_PYTHON_DISTUTILS_BUILD_OPTSoptions are already + passed automatically by the infrastructure. + -
+
PYTHON_FOO_INSTALL_TARGET_OPTS,PYTHON_FOO_INSTALL_STAGING_OPTS, +HOST_PYTHON_FOO_INSTALL_OPTSto specify additional options to pass + to the Pythonsetup.pyscript during the target installation step, + the staging installation step or the host installation, + respectively. Note that the infrastructure is automatically passing + some options, defined inPKG_PYTHON_DISTUTILS_INSTALL_TARGET_OPTS+ orPKG_PYTHON_DISTUTILS_INSTALL_STAGING_OPTS(for target distutils + packages),HOST_PKG_PYTHON_DISTUTILS_INSTALL_OPTS(for host + distutils packages),PKG_PYTHON_SETUPTOOLS_INSTALL_TARGET_OPTSor +PKG_PYTHON_SETUPTOOLS_INSTALL_STAGING_OPTS(for target setuptools + packages) andHOST_PKG_PYTHON_SETUPTOOLS_INSTALL_OPTS(for host + setuptools packages). + -
+
HOST_PYTHON_FOO_NEEDS_HOST_PYTHON, to define the host python + interpreter. The usage of this variable is limited to host + packages. The two supported value arepython2andpython3. It + will ensures the right host python package is available and will + invoke it for the build. If some build steps are overloaded, the + right python interpreter must be explicitly called in the commands. +
With the Python infrastructure, all the steps required to build and +install the packages are already defined, and they generally work well +for most Python-based packages. However, when required, it is still +possible to customize what is done in any particular step:
- +By adding a post-operation hook (after extract, patch, configure, + build or install). See Section 17.15, âHooks available in the various build stepsâ for details. +
-
+By overriding one of the steps. For example, even if the Python
+ infrastructure is used, if the package
.mkfile defines its own +PYTHON_FOO_BUILD_CMDSvariable, it will be used instead of the + default Python one. However, using this method should be restricted + to very specific cases. Do not use it in the general case. +
First, letâs see how to write a .mk file for a LuaRocks-based package,
+with an example :
01: ################################################################################ +02: # +03: # luafoo +04: # +05: ################################################################################ +06: +07: LUAFOO_VERSION = 1.0.2-1 +08: LUAFOO_DEPENDENCIES = foo +09: +10: LUAFOO_BUILD_OPTS += FOO_INCDIR=$(STAGING_DIR)/usr/include +11: LUAFOO_BUILD_OPTS += FOO_LIBDIR=$(STAGING_DIR)/usr/lib +12: LUAFOO_LICENSE = luaFoo license +13: LUAFOO_LICENSE_FILES = COPYING +14: +15: $(eval $(luarocks-package))
On line 7, we declare the version of the package (the same as in the rockspec, +which is the concatenation of the upstream version and the rockspec revision, +separated by a hyphen -).
On line 8, we declare our dependencies against native libraries, so that they +are built before the build process of our package starts.
On lines 10-11, we tell Buildroot to pass custom options to LuaRocks when it is +building the package.
On lines 12-13, we specify the licensing terms for the package.
Finally, on line 15, we invoke the luarocks-package
+macro that generates all the Makefile rules that actually allows the
+package to be built.
LuaRocks is a deployment and management system for Lua modules, and supports
+various build.type: builtin, make and cmake. In the context of
+Buildroot, the luarocks-package infrastructure only supports the builtin
+mode. LuaRocks packages that use the make or cmake build mechanisms
+should instead be packaged using the generic-package and cmake-package
+infrastructures in Buildroot, respectively.
The main macro of the LuaRocks package infrastructure is luarocks-package:
+like generic-package it works by defining a number of variables providing
+metadata information about the package, and then calling luarocks-package. It
+is worth mentioning that building LuaRocks packages for the host is not
+supported, so the macro host-luarocks-package is not implemented.
Just like the generic infrastructure, the LuaRocks infrastructure works
+by defining a number of variables before calling the luarocks-package
+macro.
First, all the package metadata information variables that exist in
+the generic infrastructure also exist in the LuaRocks infrastructure:
+LUAFOO_VERSION, LUAFOO_SOURCE, LUAFOO_SITE,
+LUAFOO_DEPENDENCIES, LUAFOO_LICENSE, LUAFOO_LICENSE_FILES.
Two of them are populated by the LuaRocks infrastructure (for the
+download step). If your package is not hosted on the LuaRocks mirror
+$(BR2_LUAROCKS_MIRROR), you can override them:
-
+
LUAFOO_SITE, which defaults to$(BR2_LUAROCKS_MIRROR)+ -
+
LUAFOO_SOURCE, which defaults toluafoo-$(LUAFOO_VERSION).src.rock+
A few additional variables, specific to the LuaRocks infrastructure, are +also defined. They can be overridden in specific cases.
-
+
LUAFOO_ROCKSPEC, which defaults toluafoo-$(LUAFOO_VERSION).rockspec+ -
+
LUAFOO_SUBDIR, which defaults to +luafoo-$(LUAFOO_VERSION_WITHOUT_ROCKSPEC_REVISION)+ -
+
LUAFOO_BUILD_OPTScontains additional build options for the +luarocks buildcall. +
First, letâs see how to write a .mk file for a Perl/CPAN package,
+with an example :
01: ################################################################################ +02: # +03: # perl-foo-bar +04: # +05: ################################################################################ +06: +07: PERL_FOO_BAR_VERSION = 0.02 +08: PERL_FOO_BAR_SOURCE = Foo-Bar-$(PERL_FOO_BAR_VERSION).tar.gz +09: PERL_FOO_BAR_SITE = $(BR2_CPAN_MIRROR)/authors/id/M/MO/MONGER +10: PERL_FOO_BAR_DEPENDENCIES = perl-strictures +11: PERL_FOO_BAR_LICENSE = Artistic or GPLv1+ +12: PERL_FOO_BAR_LICENSE_FILES = LICENSE +13: +14: $(eval $(perl-package))
On line 7, we declare the version of the package.
On line 8 and 9, we declare the name of the tarball and the location +of the tarball on a CPAN server. Buildroot will automatically download +the tarball from this location.
On line 10, we declare our dependencies, so that they are built +before the build process of our package starts.
On line 11 and 12, we give licensing details about the package (its +license on line 11, and the file containing the license text on line +12).
Finally, on line 14, we invoke the perl-package macro that
+generates all the Makefile rules that actually allow the package to be
+built.
Most of these data can be retrieved from https://metacpan.org/.
+So, this file and the Config.in can be generated by running
+the script supports/scripts/scancpan Foo-Bar in the Buildroot directory
+(or in the BR2_EXTERNAL directory).
+This script creates a Config.in file and foo-bar.mk file for the
+requested package, and also recursively for all dependencies specified by
+CPAN. You should still manually edit the result. In particular, the
+following things should be checked.
-
+If the perl module links with a shared library that is provided by
+ another (non-perl) package, this dependency is not added automatically.
+ It has to be added manually to
PERL_FOO_BAR_DEPENDENCIES. + -
+The
package/Config.infile has to be updated manually to include the + generated Config.in files. As a hint, thescancpanscript prints out + the requiredsource "â¦"statements, sorted alphabetically. +
As a policy, packages that provide Perl/CPAN modules should all be
+named perl-<something> in Buildroot.
This infrastructure handles various Perl build systems :
+ExtUtils-MakeMaker, Module-Build and Module-Build-Tiny.
+Build.PL is always preferred when a package provides a Makefile.PL
+and a Build.PL.
The main macro of the Perl/CPAN package infrastructure is
+perl-package. It is similar to the generic-package macro. The ability to
+have target and host packages is also available, with the
+host-perl-package macro.
Just like the generic infrastructure, the Perl/CPAN infrastructure
+works by defining a number of variables before calling the
+perl-package macro.
First, all the package metadata information variables that exist in the
+generic infrastructure also exist in the Perl/CPAN infrastructure:
+PERL_FOO_VERSION, PERL_FOO_SOURCE,
+PERL_FOO_PATCH, PERL_FOO_SITE,
+PERL_FOO_SUBDIR, PERL_FOO_DEPENDENCIES,
+PERL_FOO_INSTALL_TARGET.
Note that setting PERL_FOO_INSTALL_STAGING to YES has no effect
+unless a PERL_FOO_INSTALL_STAGING_CMDS variable is defined. The perl
+infrastructure doesnât define these commands since Perl modules generally
+donât need to be installed to the staging directory.
A few additional variables, specific to the Perl/CPAN infrastructure, +can also be defined. Many of them are only useful in very specific +cases, typical packages will therefore only use a few of them.
-
+
PERL_FOO_CONF_ENV/HOST_PERL_FOO_CONF_ENV, to specify additional + environment variables to pass to theperl Makefile.PLorperl Build.PL. + By default, empty. + -
+
PERL_FOO_CONF_OPTS/HOST_PERL_FOO_CONF_OPTS, to specify additional + configure options to pass to theperl Makefile.PLorperl Build.PL. + By default, empty. + -
+
PERL_FOO_BUILD_OPTS/HOST_PERL_FOO_BUILD_OPTS, to specify additional + options to pass tomake pure_allorperl Build buildin the build step. + By default, empty. + -
+
PERL_FOO_INSTALL_TARGET_OPTS, to specify additional options to + pass tomake pure_installorperl Build installin the install step. + By default, empty. + -
+
HOST_PERL_FOO_INSTALL_OPTS, to specify additional options to + pass tomake pure_installorperl Build installin the install step. + By default, empty. +
In Buildroot, a virtual package is a package whose functionalities are +provided by one or more packages, referred to as providers. The virtual +package management is an extensible mechanism allowing the user to choose +the provider used in the rootfs.
For example, OpenGL ES is an API for 2D and 3D graphics on embedded systems.
+The implementation of this API is different for the Allwinner Tech Sunxi and
+the Texas Instruments OMAP35xx platforms. So libgles will be a virtual
+package and sunxi-mali and ti-gfx will be the providers.
In the following example, we will explain how to add a new virtual package +(something-virtual) and a provider for it (some-provider).
First, letâs create the virtual package.
The Config.in file of virtual package something-virtual should contain:
01: config BR2_PACKAGE_HAS_SOMETHING_VIRTUAL +02: bool +03: +04: config BR2_PACKAGE_PROVIDES_SOMETHING_VIRTUAL +05: depends on BR2_PACKAGE_HAS_SOMETHING_VIRTUAL +06: string
In this file, we declare two options, BR2_PACKAGE_HAS_SOMETHING_VIRTUAL and
+BR2_PACKAGE_PROVIDES_SOMETHING_VIRTUAL, whose values will be used by the
+providers.
The .mk for the virtual package should just evaluate the virtual-package macro:
01: ################################################################################ +02: # +03: # something-virtual +04: # +05: ################################################################################ +06: +07: $(eval $(virtual-package))
The ability to have target and host packages is also available, with the
+host-virtual-package macro.
When adding a package as a provider, only the Config.in file requires some
+modifications.
The Config.in file of the package some-provider, which provides the
+functionalities of something-virtual, should contain:
01: config BR2_PACKAGE_SOME_PROVIDER +02: bool "some-provider" +03: select BR2_PACKAGE_HAS_SOMETHING_VIRTUAL +04: help +05: This is a comment that explains what some-provider is. +06: +07: http://foosoftware.org/some-provider/ +08: +09: if BR2_PACKAGE_SOME_PROVIDER +10: config BR2_PACKAGE_PROVIDES_SOMETHING_VIRTUAL +11: default "some-provider" +12: endif
On line 3, we select BR2_PACKAGE_HAS_SOMETHING_VIRTUAL, and on line 11, we
+set the value of BR2_PACKAGE_PROVIDES_SOMETHING_VIRTUAL to the name of the
+provider, but only if it is selected.
See Chapter 25, List of virtual packages for the symbols to select if you implement +a new provider for an existing virtual package.
The .mk file should also declare an additional variable
+SOME_PROVIDER_PROVIDES to contain the names of all the virtual
+packages it is an implementation of:
01: SOME_PROVIDER_PROVIDES = something-virtual
Of course, do not forget to add the proper build and runtime dependencies for +this package!
See Chapter 25, List of virtual packages for the names of virtual packages to provide +if you implement a new provider for an existing virtual package.
When adding a package that requires a certain FEATURE provided by a virtual
+package, you have to use depends on BR2_PACKAGE_HAS_FEATURE, like so:
config BR2_PACKAGE_HAS_FEATURE + bool + +config BR2_PACKAGE_FOO + bool "foo" + depends on BR2_PACKAGE_HAS_FEATURE
If your package really requires a specific provider, then youâll have to
+make your package depends on this provider; you can not select a
+provider.
Letâs take an example with two providers for a FEATURE:
config BR2_PACKAGE_HAS_FEATURE + bool + +config BR2_PACKAGE_FOO + bool "foo" + select BR2_PACKAGE_HAS_FEATURE + +config BR2_PACKAGE_BAR + bool "bar" + select BR2_PACKAGE_HAS_FEATURE
And you are adding a package that needs FEATURE as provided by foo,
+but not as provided by bar.
If you were to use select BR2_PACKAGE_FOO, then the user would still
+be able to select BR2_PACKAGE_BAR in the menuconfig. This would create
+a configuration inconsistency, whereby two providers of the same FEATURE
+would be enabled at once, one explicitly set by the user, the other
+implicitly by your select.
Instead, you have to use depends on BR2_PACKAGE_FOO, which avoids any
+implicit configuration inconsistency.
A popular way for a software package to handle user-specified
+configuration is kconfig. Among others, it is used by the Linux
+kernel, Busybox, and Buildroot itself. The presence of a .config file
+and a menuconfig target are two well-known symptoms of kconfig being
+used.
Buildroot features an infrastructure for packages that use kconfig for
+their configuration. This infrastructure provides the necessary logic to
+expose the packageâs menuconfig target as foo-menuconfig in
+Buildroot, and to handle the copying back and forth of the configuration
+file in a correct way.
The kconfig-package infrastructure is based on the generic-package
+infrastructure. All variables supported by generic-package are
+available in kconfig-package as well. See
+Section 17.5.2, âgeneric-package referenceâ for more details.
In order to use the kconfig-package infrastructure for a Buildroot
+package, the minimally required lines in the .mk file, in addition to
+the variables required by the generic-package infrastructure, are:
FOO_KCONFIG_FILE = reference-to-source-configuration-file + +$(eval $(kconfig-package))
This snippet creates the following make targets:
-
+
foo-menuconfig, which calls the packageâsmenuconfigtarget + -
+
foo-update-config, which copies the configuration back to the source + configuration file. +
and ensures that the source configuration file is copied to the build +directory at the right moment.
In addition to these minimally required lines, several optional variables can +be set to suit the needs of the package under consideration:
-
+
FOO_KCONFIG_EDITORS: a space-separated list of kconfig editors to + support, for example menuconfig xconfig. By default, menuconfig. + -
+
FOO_KCONFIG_OPTS: extra options to pass when calling the kconfig + editors. This may need to include $(FOO_MAKE_OPTS), for example. By + default, empty. + -
+
FOO_KCONFIG_FIXUP_CMDS: a list of shell commands needed to fixup the + configuration file after copying it or running a kconfig editor. Such + commands may be needed to ensure a configuration consistent with other + configuration of Buildroot, for example. By default, empty. +
First, letâs see how to write a .mk file for a rebar-based package,
+with an example :
01: ################################################################################ +02: # +03: # erlang-foobar +04: # +05: ################################################################################ +06: +07: ERLANG_FOOBAR_VERSION = 1.0 +08: ERLANG_FOOBAR_SOURCE = erlang-foobar-$(ERLANG_FOOBAR_VERSION).tar.xz +09: ERLANG_FOOBAR_SITE = http://www.foosoftware.org/download +10: ERLANG_FOOBAR_DEPENDENCIES = host-libaaa libbbb +11: +12: $(eval $(rebar-package))
On line 7, we declare the version of the package.
On line 8 and 9, we declare the name of the tarball (xz-ed tarball +recommended) and the location of the tarball on the Web. Buildroot +will automatically download the tarball from this location.
On line 10, we declare our dependencies, so that they are built +before the build process of our package starts.
Finally, on line 12, we invoke the rebar-package macro that
+generates all the Makefile rules that actually allows the package to
+be built.
The main macro of the rebar package infrastructure is
+rebar-package. It is similar to the generic-package macro. The
+ability to have host packages is also available, with the
+host-rebar-package macro.
Just like the generic infrastructure, the rebar infrastructure works
+by defining a number of variables before calling the rebar-package
+macro.
First, all the package metadata information variables that exist in
+the generic infrastructure also exist in the rebar infrastructure:
+ERLANG_FOOBAR_VERSION, ERLANG_FOOBAR_SOURCE,
+ERLANG_FOOBAR_PATCH, ERLANG_FOOBAR_SITE,
+ERLANG_FOOBAR_SUBDIR, ERLANG_FOOBAR_DEPENDENCIES,
+ERLANG_FOOBAR_INSTALL_STAGING, ERLANG_FOOBAR_INSTALL_TARGET,
+ERLANG_FOOBAR_LICENSE and ERLANG_FOOBAR_LICENSE_FILES.
A few additional variables, specific to the rebar infrastructure,
+can also be defined. Many of them are only useful in very specific
+cases, typical packages will therefore only use a few of them.
+
ERLANG_FOOBAR_USE_AUTOCONF, to specify that the package uses + autoconf at the configuration step. When a package sets this + variable toYES, theautotoolsinfrastructure is used. +Note. You can also use some of the variables from the
autotools+ infrastructure:ERLANG_FOOBAR_CONF_ENV,ERLANG_FOOBAR_CONF_OPTS, +ERLANG_FOOBAR_AUTORECONF,ERLANG_FOOBAR_AUTORECONF_ENVand +ERLANG_FOOBAR_AUTORECONF_OPTS.+
ERLANG_FOOBAR_USE_BUNDLED_REBAR, to specify that the package has + a bundled version of rebar and that it shall be used. Valid + values areYESorNO(the default). +Note. If the package bundles a rebar utility, but can use the generic + one that Buildroot provides, just say
NO(i.e., do not specify + this variable). Only set if it is mandatory to use the rebar + utility bundled in this package.-
+
ERLANG_FOOBAR_REBAR_ENV, to specify additional environment + variables to pass to the rebar utility. +
With the rebar infrastructure, all the steps required to build +and install the packages are already defined, and they generally work +well for most rebar-based packages. However, when required, it is +still possible to customize what is done in any particular step:
- +By adding a post-operation hook (after extract, patch, configure, + build or install). See Section 17.15, âHooks available in the various build stepsâ for details. +
-
+By overriding one of the steps. For example, even if the rebar
+ infrastructure is used, if the package
.mkfile defines its + ownERLANG_FOOBAR_BUILD_CMDSvariable, it will be used instead + of the default rebar one. However, using this method should be + restricted to very specific cases. Do not use it in the general + case. +
The Buildroot manual, which you are currently reading, is entirely written +using the AsciiDoc mark-up syntax. The manual is then +rendered to many formats:
- +html +
- +split-html +
- +pdf +
- +epub +
- +text +
Although Buildroot only contains one document written in AsciiDoc, there +is, as for packages, an infrastructure for rendering documents using the +AsciiDoc syntax.
Also as for packages, the AsciiDoc infrastructure is available from +BR2_EXTERNAL +Section 9.2, âKeeping customizations outside of Buildrootâ. This allows documentation for a +BR2_EXTERNAL tree to match the Buildroot documentation, as it will be +rendered to the same formats and use the same layout and theme.
Whereas package infrastructures are suffixed with -package, the document
+infrastructures are suffixed with -document. So, the AsciiDoc infrastructure
+is named asciidoc-document.
Here is an example to render a simple AsciiDoc document.
01: ################################################################################ +02: # +03: # foo-document +04: # +05: ################################################################################ +06: +07: FOO_SOURCES = $(sort $(wildcard $(pkgdir)/*)) +08: $(eval $(call asciidoc-document))
On line 7, the Makefile declares what the sources of the document are. +Currently, it is expected that the documentâs sources are only local; +Buildroot will not attempt to download anything to render a document. +Thus, you must indicate where the sources are. Usually, the string +above is sufficient for a document with no sub-directory structure.
On line 8, we call the asciidoc-document function, which generates all
+the Makefile code necessary to render the document.
The list of variables that can be set in a .mk file to give metadata
+information is (assuming the document name is foo) :
-
+
FOO_SOURCES, mandatory, defines the source files for the document. + -
+
FOO_RESOURCES, optional, may contain a space-separated list of paths + to one or more directories containing so-called resources (like CSS or + images). By default, empty. +
There are also additional hooks (see Section 17.15, âHooks available in the various build stepsâ for general information +on hooks), that a document may set to define extra actions to be done at +various steps:
-
+
FOO_POST_RSYNC_HOOKSto run additional commands after the sources + have been copied by Buildroot. This can for example be used to + generate part of the manual with information extracted from the + tree. As an example, Buildroot uses this hook to generate the tables + in the appendices. + -
+
FOO_CHECK_DEPENDENCIES_HOOKSto run additional tests on required + components to generate the document. In AsciiDoc, it is possible to + call filters, that is, programs that will parse an AsciiDoc block and + render it appropriately (e.g. ditaa or + aafigure). + -
+
FOO_CHECK_DEPENDENCIES_<FMT>_HOOKS, to run additional tests for + the specified format<FMT>(see the list of rendered formats, above). +
Here is a complete example that uses all variables and all hooks:
01: ################################################################################ +02: # +03: # foo-document +04: # +05: ################################################################################ +06: +07: FOO_SOURCES = $(sort $(wildcard $(pkgdir)/*)) +08: FOO_RESOURCES = $(sort $(wildcard $(pkgdir)/ressources)) +09: +10: define FOO_GEN_EXTRA_DOC +11: /path/to/generate-script --outdir=$(@D) +12: endef +13: FOO_POST_RSYNC_HOOKS += FOO_GEN_EXTRA_DOC +14: +15: define FOO_CHECK_MY_PROG +16: if ! which my-prog >/dev/null 2>&1; then \ +17: echo "You need my-prog to generate the foo document"; \ +18: exit 1; \ +19: fi +20: endef +21: FOO_CHECK_DEPENDENCIES_HOOKS += FOO_CHECK_MY_PROG +22: +23: define FOO_CHECK_MY_OTHER_PROG +24: if ! which my-other-prog >/dev/null 2>&1; then \ +25: echo "You need my-other-prog to generate the foo document as PDF"; \ +26: exit 1; \ +27: fi +28: endef +29: FOO_CHECK_DEPENDENCIES_PDF_HOOKS += FOO_CHECK_MY_OTHER_PROG +30: +31: $(eval $(call asciidoc-document))
The generic infrastructure (and as a result also the derived autotools
+and cmake infrastructures) allow packages to specify hooks.
+These define further actions to perform after existing steps.
+Most hooks arenât really useful for generic packages, since the .mk
+file already has full control over the actions performed in each step
+of the package construction.
The following hook points are available:
-
+
LIBFOO_PRE_DOWNLOAD_HOOKS+ -
+
LIBFOO_POST_DOWNLOAD_HOOKS+ -
+
LIBFOO_PRE_EXTRACT_HOOKS+ -
+
LIBFOO_POST_EXTRACT_HOOKS+ -
+
LIBFOO_PRE_RSYNC_HOOKS+ -
+
LIBFOO_POST_RSYNC_HOOKS+ -
+
LIBFOO_PRE_PATCH_HOOKS+ -
+
LIBFOO_POST_PATCH_HOOKS+ -
+
LIBFOO_PRE_CONFIGURE_HOOKS+ -
+
LIBFOO_POST_CONFIGURE_HOOKS+ -
+
LIBFOO_PRE_BUILD_HOOKS+ -
+
LIBFOO_POST_BUILD_HOOKS+ -
+
LIBFOO_PRE_INSTALL_HOOKS(for host packages only) + -
+
LIBFOO_POST_INSTALL_HOOKS(for host packages only) + -
+
LIBFOO_PRE_INSTALL_STAGING_HOOKS(for target packages only) + -
+
LIBFOO_POST_INSTALL_STAGING_HOOKS(for target packages only) + -
+
LIBFOO_PRE_INSTALL_TARGET_HOOKS(for target packages only) + -
+
LIBFOO_POST_INSTALL_TARGET_HOOKS(for target packages only) + -
+
LIBFOO_PRE_INSTALL_IMAGES_HOOKS+ -
+
LIBFOO_POST_INSTALL_IMAGES_HOOKS+ -
+
LIBFOO_PRE_LEGAL_INFO_HOOKS+ -
+
LIBFOO_POST_LEGAL_INFO_HOOKS+
These variables are lists of variable names containing actions to be +performed at this hook point. This allows several hooks to be +registered at a given hook point. Here is an example:
define LIBFOO_POST_PATCH_FIXUP + action1 + action2 +endef + +LIBFOO_POST_PATCH_HOOKS += LIBFOO_POST_PATCH_FIXUP
The POST_RSYNC hook is run only for packages that use a local source,
+either through the local site method or the OVERRIDE_SRCDIR
+mechanism. In this case, package sources are copied using rsync from
+the local location into the buildroot build directory. The rsync
+command does not copy all files from the source directory, though.
+Files belonging to a version control system, like the directories
+.git, .hg, etc. are not copied. For most packages this is
+sufficient, but a given package can perform additional actions using
+the POST_RSYNC hook.
In principle, the hook can contain any command you want. One specific
+use case, though, is the intentional copying of the version control
+directory using rsync. The rsync command you use in the hook can, among
+others, use the following variables:
-
+
$(SRCDIR): the path to the overridden source directory + -
+
$(@D): the path to the build directory +
Many packages that support internationalization use the gettext +library. Dependencies for this library are fairly complicated and +therefore, deserve some explanation.
The uClibc C library doesnât implement gettext functionality;
+therefore with this C library, a separate gettext must be compiled,
+which is provided by the additional libintl library, part of the
+gettext package.
On the other hand, the glibc C library does integrate its own
+gettext library functions, so it is not necessary to build a separate
+libintl library.
However, certain packages need some gettext utilities on the target,
+such as the gettext program itself, which allows to retrieve
+translated strings, from the command line.
Additionally, some packages (such as libglib2) do require gettext
+functions unconditionally, while other packages (in general, those who
+support --disable-nls) only require gettext functions when locale
+support is enabled.
Therefore, Buildroot defines two configuration options:
-
+
BR2_NEEDS_GETTEXT, which is true as soon as the toolchain doesnât + provide its own gettext implementation + -
+
BR2_NEEDS_GETTEXT_IF_LOCALE, which is true if the toolchain + doesnât provide its own gettext implementation and if locale support + is enabled +
Packages that need gettext only when locale support is enabled should:
-
+use
select BR2_PACKAGE_GETTEXT if BR2_NEEDS_GETTEXT_IF_LOCALEin the +Config.infile; + -
+use
$(if $(BR2_NEEDS_GETTEXT_IF_LOCALE),gettext)in the package +DEPENDENCIESvariable in the.mkfile. +
Packages that unconditionally need gettext (which should be very rare) +should:
-
+use
select BR2_PACKAGE_GETTEXT if BR2_NEEDS_GETTEXTin theConfig.in+ file; + -
+use
$(if $(BR2_NEEDS_GETTEXT),gettext)in the package +DEPENDENCIESvariable in the.mkfile. +
Packages that need the gettext utilities on the target (should be
+rare) should:
-
+use
select BR2_PACKAGE_GETTEXTin theirConfig.infile, + indicating in a comment above that itâs a runtime dependency only. + -
+not add any
gettextdependency in theDEPENDENCIESvariable of + their.mkfile. +
In Buildroot, there is some relationship between:
-
+the package name, which is the package directory name (and the
+ name of the
*.mkfile); + -
+the config entry name that is declared in the
Config.infile; + - +the makefile variable prefix. +
It is mandatory to maintain consistency between these elements, +using the following rules:
-
+the package directory and the
*.mkname are the package name + itself (e.g.:package/foo-bar_boo/foo-bar_boo.mk); + -
+the make target name is the package name itself (e.g.:
+
foo-bar_boo); + -
+the config entry is the upper case package name with
.and-+ characters substituted with_, prefixed withBR2_PACKAGE_(e.g.: +BR2_PACKAGE_FOO_BAR_BOO); + -
+the
*.mkfile variable prefix is the upper case package name + with.and-characters substituted with_(e.g.: +FOO_BAR_BOO_VERSION). +
Packages on GitHub often donât have a download area with release tarballs. +However, it is possible to download tarballs directly from the repository +on GitHub. As GitHub is known to have changed download mechanisms in the +past, the github helper function should be used as shown below.
# Use a tag or a full commit ID +FOO_VERSION = v1.0 +FOO_SITE = $(call github,<user>,<package>,$(FOO_VERSION))
Notes
- +The FOO_VERSION can either be a tag or a commit ID. +
-
+The tarball name generated by github matches the default one from
+ Buildroot (e.g.:
foo-f6fb6654af62045239caed5950bc6c7971965e60.tar.gz), + so it is not necessary to specify it in the.mkfile. + - +When using a commit ID as version, you should use the full 40 hex characters. +
If the package you wish to add does have a release section on GitHub, the +maintainer may have uploaded a release tarball, or the release may just point +to the automatically generated tarball from the git tag. If there is a +release tarball uploaded by the maintainer, we prefer to use that since it +may be slightly different (e.g. it contains a configure script so we donât +need to do AUTORECONF).
You can see on the release page if itâs an uploaded tarball or a git tag:
-
+If there is a green download button, like
+ mongrel2, then it
+ was uploaded by the maintainer and you should use the link of that button to
+ specify
FOO_SITE, and not use the github helper. + - +If there is grey download button, like + xbmc, then itâs an + automatically generated tarball and you should use the github helper + function. +
As you can see, adding a software package to Buildroot is simply a +matter of writing a Makefile using an existing example and modifying it +according to the compilation process required by the package.
If you package software that might be useful for other people, donât +forget to send a patch to the Buildroot mailing list (see +Section 21.5, âSubmitting patchesâ)!
While integrating a new package or updating an existing one, it may be +necessary to patch the source of the software to get it cross-built within +Buildroot.
Buildroot offers an infrastructure to automatically handle this during +the builds. It supports three ways of applying patch sets: downloaded patches, +patches supplied within buildroot and patches located in a user-defined +global patch directory.
If it is necessary to apply a patch that is available for download, then add it
+to the <packagename>_PATCH variable. It is downloaded from the same site
+as the package itself. It can be a single patch, or a tarball containing a
+patch series.
This method is typically used for packages from Debian.
Most patches are provided within Buildroot, in the package +directory; these typically aim to fix cross-compilation, libc support, +or other such issues.
These patch files should be named <number>-<description>.patch.
Notes
- +The patch files coming with Buildroot should not contain any package version + reference in their filename. +
-
+The field
<number>in the patch file name refers to the apply order, + and shall start at 1; It is preferred to pad the number with zeros up to 4 + digits, like git-format-patch does. E.g.:0001-foobar-the-buz.patch+ -
+Previously, it was mandatory for patches to be prefixed with the name of
+ the package, like
<package>-<number>-<description>.patch, but that is + no longer the case. Existing packages will be fixed as time passes. Do + not prefix patches with the package name. + -
+Previously, a
seriesfile, as used byquilt, could also be added in + the package directory. In that case, theseriesfile defines the patch + application order. This is deprecated, and will be removed in the future. + Do not use a series file. +
The BR2_GLOBAL_PATCH_DIR configuration file option can be
+used to specify a space separated list of one or more directories
+containing global package patches. See Section 9.8, âAdding project-specific patchesâ for
+details.
-
+Run the
<packagename>_PRE_PATCH_HOOKScommands if defined; + -
+Cleanup the build directory, removing any existing
*.rejfiles; + -
+If
<packagename>_PATCHis defined, then patches from these + tarballs are applied; + +If there are some
*.patchfiles in the packageâs Buildroot + directory or in a package subdirectory named<packageversion>, + then: +-
+If a
seriesfile exists in the package directory, then patches are + applied according to theseriesfile; + -
+Otherwise, patch files matching
<packagename>-*.patch+ are applied in alphabetical order. + So, to ensure they are applied in the right order, it is highly + recommended to name the patch files like this: +<packagename>-<number>-<description>.patch, where<number>+ refers to the apply order. +
-
+If a
-
+If
BR2_GLOBAL_PATCH_DIRis defined, the directories will be + enumerated in the order they are specified. The patches are applied + as described in the previous step. + -
+Run the
<packagename>_POST_PATCH_HOOKScommands if defined. +
If something goes wrong in the steps 3 or 4, then the build fails.
Patches are released under the same license as the software that is +modified.
A message explaining what the patch does, and why it is needed, should +be added in the header commentary of the patch.
You should add a Signed-off-by statement in the header of the each
+patch to help with keeping track of the changes and to certify that the
+patch is released under the same license as the software that is modified.
If the software is under version control, it is recommended to use the +upstream SCM software to generate the patch set.
Otherwise, concatenate the header with the output of the
+diff -purN package-version.orig/ package-version/ command.
At the end, the patch should look like:
configure.ac: add C++ support test + +Signed-off-by: John Doe <john.doe@noname.org> + +--- configure.ac.orig ++++ configure.ac +@@ -40,2 +40,12 @@ + +AC_PROG_MAKE_SET ++ ++AC_CACHE_CHECK([whether the C++ compiler works], ++ [rw_cv_prog_cxx_works], ++ [AC_LANG_PUSH([C++]) ++ AC_LINK_IFELSE([AC_LANG_PROGRAM([], [])], ++ [rw_cv_prog_cxx_works=yes], ++ [rw_cv_prog_cxx_works=no]) ++ AC_LANG_POP([C++])]) ++ ++AM_CONDITIONAL([CXX_WORKS], [test "x$rw_cv_prog_cxx_works" = "xyes"])
When integrating a patch of which you are not the author, you have to +add a few things in the header of the patch itself.
Depending on whether the patch has been obtained from the project +repository itself, or from somewhere on the web, add one of the +following tags:
Backported from: <some commit id>
or
Fetch from: <some url>
It is also sensible to add a few words about any changes to the patch +that may have been necessary.
It is possible to instrument the steps Buildroot does when building
+packages. Define the variable BR2_INSTRUMENTATION_SCRIPTS to contain
+the path of one or more scripts (or other executables), in a
+space-separated list, you want called before and after each step. The
+scripts are called in sequence, with three parameters:
-
+
startorendto denote the start (resp. the end) of a step; + - +the name of the step about to be started, or which just ended; +
- +the name of the package. +
For example :
make BR2_INSTRUMENTATION_SCRIPTS="/path/to/my/script1 /path/to/my/script2"
The list of steps is:
-
+
extract+ -
+
patch+ -
+
configure+ -
+
build+ -
+
install-host, when a host-package is installed in$(HOST_DIR)+ -
+
install-target, when a target-package is installed in$(TARGET_DIR)+ -
+
install-staging, when a target-package is installed in$(STAGING_DIR)+ -
+
install-image, when a target-package installs files in$(BINARIES_DIR)+
The script has access to the following variables:
-
+
BR2_CONFIG: the path to the Buildroot .config file + -
+
HOST_DIR,STAGING_DIR,TARGET_DIR: see + Section 17.5.2, âgeneric-packagereferenceâ + -
+
BUILD_DIR: the directory where packages are extracted and built + -
+
BINARIES_DIR: the place where all binary files (aka images) are + stored + -
+
BASE_DIR: the base output directory +
There are many ways in which you can contribute to Buildroot: analyzing +and fixing bugs, analyzing and fixing package build failures detected by +the autobuilders, testing and reviewing patches sent by other +developers, working on the items in our TODO list and sending your own +improvements to Buildroot or its manual. The following sections give a +little more detail on each of these items.
If you are interested in contributing to Buildroot, the first thing you +should do is to subscribe to the Buildroot mailing list. This list is +the main way of interacting with other Buildroot developers and to send +contributions to. If you arenât subscribed yet, then refer to +Chapter 5, Community resources for the subscription link.
If you are going to touch the code, it is highly recommended to use a +git repository of Buildroot, rather than starting from an extracted +source code tarball. Git is the easiest way to develop from and directly +send your patches to the mailing list. Refer to Chapter 3, Getting Buildroot +for more information on obtaining a Buildroot git tree.
A first way of contributing is to have a look at the open bug reports in +the Buildroot bug +tracker. As we strive to keep the bug count as small as possible, all +help in reproducing, analyzing and fixing reported bugs is more than +welcome. Donât hesitate to add a comment to bug reports reporting your +findings, even if you donât yet see the full picture.
The Buildroot autobuilders are a set of build machines that continuously +run Buildroot builds based on random configurations. This is done for +all architectures supported by Buildroot, with various toolchains, and +with a random selection of packages. With the large commit activity on +Buildroot, these autobuilders are a great help in detecting problems +very early after commit.
All build results are available at http://autobuild.buildroot.org, +statistics are at http://autobuild.buildroot.org/stats.php. Every day, +an overview of all failed packages is sent to the mailing list.
Detecting problems is great, but obviously these problems have to be +fixed as well. Your contribution is very welcome here! There are +basically two things that can be done:
- +Analyzing the problems. The daily summary mails do not contain details + about the actual failures: in order to see whatâs going on you have to + open the build log and check the last output. Having someone doing + this for all packages in the mail is very useful for other developers, + as they can make a quick initial analysis based on this output alone. +
+Fixing a problem. When fixing autobuild failures, you should follow + these steps: +
- +Check if you can reproduce the problem by building with the same + configuration. You can do this manually, or use the + br-reproduce-build + script that will automatically clone a Buildroot git repository, + checkout the correct revision, download and set the right + configuration, and start the build. +
- +Analyze the problem and create a fix. +
- +Verify that the problem is really fixed by starting from a clean + Buildroot tree and only applying your fix. +
- +Send the fix to the Buildroot mailing list (see + Section 21.5, âSubmitting patchesâ). In case you created a patch against the + package sources, you should also send the patch upstream so that the + problem will be fixed in a later release, and the patch in Buildroot + can be removed. + In the commit message of a patch fixing an autobuild failure, add a + reference to the build result directory, as follows: +
Fixes http://autobuild.buildroot.org/results/51000a9d4656afe9e0ea6f07b9f8ed374c2e4069
With the amount of patches sent to the mailing list each day, the +maintainer has a very hard job to judge which patches are ready to apply +and which ones arenât. Contributors can greatly help here by reviewing +and testing these patches.
In the review process, do not hesitate to respond to patch submissions +for remarks, suggestions or anything that will help everyone to +understand the patches and make them better. Please use internet +style replies in plain text emails when responding to patch +submissions.
To indicate approval of a patch, there are three formal tags that keep +track of this approval. To add your tag to a patch, reply to it with the +approval tag below the original authorâs Signed-off-by line. These tags +will be picked up automatically by patchwork (see +Section 21.3.1, âApplying Patches from Patchworkâ) and will be part of the commit log when +the patch is accepted.
- +Tested-by +
- +Indicates that the patch has been tested successfully. + You are encouraged to specify what kind of testing you performed + (compile-test on architecture X and Y, runtime test on target A, + â¦). This additional information helps other testers and the + maintainer. +
- +Reviewed-by +
- +Indicates that you code-reviewed the patch and did your + best in spotting problems, but you are not sufficiently familiar with + the area touched to provide an Acked-by tag. This means that there + may be remaining problems in the patch that would be spotted by + someone with more experience in that area. Should such problems be + detected, your Reviewed-by tag remains appropriate and you cannot + be blamed. +
- +Acked-by +
- +Indicates that you code-reviewed the patch and you are + familiar enough with the area touched to feel that the patch can be + committed as-is (no additional changes required). In case it later + turns out that something is wrong with the patch, your Acked-by could + be considered inappropriate. The difference between Acked-by and + Reviewed-by is thus mainly that you are prepared to take the blame on + Acked patches, but not on Reviewed ones. +
If you reviewed a patch and have comments on it, you should simply reply +to the patch stating these comments, without providing a Reviewed-by or +Acked-by tag. These tags should only be provided if you judge the patch +to be good as it is.
It is important to note that neither Reviewed-by nor Acked-by imply +that testing has been performed. To indicate that you both reviewed and +tested the patch, provide two separate tags (Reviewed/Acked-by and +Tested-by).
Note also that any developer can provide Tested/Reviewed/Acked-by +tags, without exception, and we encourage everyone to do this. Buildroot +does not have a defined group of core developers, it just so happens +that some developers are more active than others. The maintainer will +value tags according to the track record of their submitter. Tags +provided by a regular contributor will naturally be trusted more than +tags provided by a newcomer. As you provide tags more regularly, your +trustworthiness (in the eyes of the maintainer) will go up, but any +tag provided is valuable.
Buildrootâs Patchwork website can be used to pull in patches for testing +purposes. Please see Section 21.3.1, âApplying Patches from Patchworkâ for more +information on using Buildrootâs Patchwork website to apply patches.
The main use of Buildrootâs Patchwork website for a developer is for +pulling in patches into their local git repository for testing +purposes.
When browsing patches in the patchwork management interface, an mbox
+link is provided at the top of the page. Copy this link address and
+run the following commands:
$ git checkout -b <test-branch-name> +$ wget -O - <mbox-url> | git am
Another option for applying patches is to create a bundle. A bundle is
+a set of patches that you can group together using the patchwork
+interface. Once the bundle is created and the bundle is made public,
+you can copy the mbox link for the bundle and apply the bundle
+using the above commands.
If you want to contribute to Buildroot but donât know where to start, +and you donât like any of the above topics, you can always work on items +from the Buildroot TODO list. +Donât hesitate to discuss an item first on the mailing list or on IRC. +Do edit the wiki to indicate when you start working on an item, so we +avoid duplicate efforts.
Note
Please, do not attach patches to bugs, send them to the mailing list +instead.
If you made some changes to Buildroot and you would like to contribute +them to the Buildroot project, proceed as follows. Starting from the +changes committed in your local git view, rebase your development +branch on top of the upstream tree before generating a patch set. To do +so, run:
$ git fetch --all --tags +$ git rebase origin/master
Now, you are ready to generate then submit your patch set.
To generate it, run:
$ git format-patch -M -n -s -o outgoing origin/master
This will generate patch files in the outgoing subdirectory,
+automatically adding the Signed-off-by line.
Once patch files are generated, you can review/edit the commit message +before submitting them, using your favorite text editor.
Lastly, send/submit your patch set to the Buildroot mailing list:
$ git send-email --to buildroot@buildroot.org outgoing/*
Note that git should be configured to use your mail account.
+To configure git, see man git-send-email or google it.
If you do not use git send-email, make sure posted patches are not
+line-wrapped, otherwise they cannot easily be applied. In such a case,
+fix your e-mail client, or better yet, learn to use git send-email.
If you want to present the whole patch set in a separate mail, add
+--cover-letter to the git format-patch command (see man
+git-format-patch for further information). This will generate a
+template for an introduction e-mail to your patch series.
A cover letter may be useful to introduce the changes you propose +in the following cases:
- +large number of commits in the series; +
- +deep impact of the changes in the rest of the project; +
- +RFC [4]; +
- +whenever you feel it will help presenting your work, your choices, + the review process, etc. +
When improvements are requested, the new revision of each commit
+should include a changelog of the modifications between each
+submission. Note that when your patch series is introduced by a cover
+letter, an overall changelog may be added to the cover letter in
+addition to the changelog in the individual commits.
+The best thing to rework a patch series is by interactive rebasing:
+git rebase -i origin/master. Consult the git manual for more
+information.
When added to the individual commits, this changelog is added when
+editing the commit message. Below the Signed-off-by section, add
+--- and your changelog.
Although the changelog will be visible for the reviewers in the mail
+thread, as well as in patchwork, git
+will automatically ignores lines below --- when the patch will be
+merged. This is the intended behavior: the changelog is not meant to
+be preserved forever in the git history of the project.
Hereafter the recommended layout:
Patch title: short explanation, max 72 chars + +A paragraph that explains the problem, and how it manifests itself. If +the problem is complex, it is OK to add more paragraphs. All paragraphs +should be wrapped at 72 characters. + +A paragraph that explains the root cause of the problem. Again, more +than on paragraph is OK. + +Finally, one or more paragraphs that explain how the problem is solved. +Don't hesitate to explain complex solutions in detail. + +Signed-off-by: John DOE <john.doe@example.net> + +--- +Changes v2 -> v3: + - foo bar (suggested by Jane) + - bar buz + +Changes v1 -> v2: + - alpha bravo (suggested by John) + - charly delta
Any patch revision should include the version number. The version number
+is simply composed of the letter v followed by an integer greater or
+equal to two (i.e. "PATCH v2", "PATCH v3" â¦).
This can be easily handled with git format-patch by using the option
+--subject-prefix:
$ git format-patch --subject-prefix "PATCH v4" \ + -M -s -o outgoing origin/master
Before reporting any issue, please check in +the mailing list archive +Chapter 5, Community resources whether someone has +already reported and/or fixed a similar problem.
However you choose to report bugs or get help, either by +opening a bug in the bug tracker +Chapter 5, Community resources or by +sending a mail to the mailing list +Chapter 5, Community resources, there are +a number of details to provide in order to help people reproduce and +find a solution to the issue.
Try to think as if you were trying to help someone else; in +that case, what would you need?
Here is a short list of details to provide in such case:
- +host machine (OS/release) +
- +version of Buildroot +
- +target for which the build fails +
- +package(s) for which the build fails +
- +the command that fails and its output +
- +any information you think that may be relevant +
Additionally, you should add the .config file (or if you know how, a
+defconfig; see Section 9.3, âStoring the Buildroot configurationâ).
If some of these details are too large, do not hesitate to use a +pastebin service. Note that not all available pastebin services will +preserve Unix-style line terminators when downloading raw pastes. +Following pastebin services are known to work correctly: +- https://gist.github.com/ +- http://code.bulix.org/
The makedev syntax is used in several places in Buildroot to +define changes to be made for permissions, or which device files to +create and how to create them, in order to avoid calls to mknod.
This syntax is derived from the makedev utility, and more complete
+documentation can be found in the package/makedevs/README file.
It takes the form of a space separated list of fields, one file per +line; the fields are:
name | type | mode | uid | gid | major | minor | start | inc | count |
There are a few non-trivial blocks:
-
+
nameis the path to the file you want to create/modify + +
typeis the type of the file, being one of: +- +f: a regular file +
- +d: a directory +
- +r: a directory recursively +
- +c: a character device file +
- +b: a block device file +
- +p: a named pipe +
-
+
mode,uidandgidare the usual permissions settings + -
+
majorandminorare here for device files - set to - for other + files + -
+
start,incandcountare for when you want to create a batch + of files, and can be reduced to a loop, beginning atstart, + incrementing its counter byincuntil it reachescount+
Letâs say you want to change the permissions of a given file; using +this syntax, you will need to put:
/usr/bin/foobar f 644 0 0 - - - - -
Alternatively, if you want to change owner/permission of a directory +recursively, you can put:
/usr/share/myapp r 750 myuser myuser - - - - -
On the other hand, if you want to create the device file /dev/hda
+and the corresponding 15 files for the partitions, you will need for
+/dev/hda:
/dev/hda b 640 0 0 3 0 0 0 -
and then for device files corresponding to the partitions of
+/dev/hda, /dev/hdaX, X ranging from 1 to 15:
/dev/hda b 640 0 0 3 1 1 1 15
The syntax to create users is inspired by the makedev syntax, above, but +is specific to Buildroot.
The syntax for adding a user is a space-separated list of fields, one +user per line; the fields are:
username | uid | group | gid | password | home | shell | groups | comment |
Where:
-
+
usernameis the desired user name (aka login name) for the user. + It can not beroot, and must be unique. If set to-, then just a + group will be created. + -
+
uidis the desired UID for the user. It must be unique, and not +0. If set to-1, then a unique UID will be computed by Buildroot + in the range [1000â¦1999] + -
+
groupis the desired name for the userâs main group. It can not + beroot. If the group does not exist, it will be created. + -
+
gidis the desired GID for the userâs main group. It must be unique, + and not0. If set to-1, and the group does not already exist, then + a unique GID will be computed by Buildroot in the range [1000..1999] + -
+
passwordis the crypt(3)-encoded password. If prefixed with!, + then login is disabled. If prefixed with=, then it is interpreted + as clear-text, and will be crypt-encoded (using MD5). If prefixed with +!=, then the password will be crypt-encoded (using MD5) and login + will be disabled. If set to*, then login is not allowed. + -
+
homeis the desired home directory for the user. If set to -, no + home directory will be created, and the userâs home will be/. + Explicitly settinghometo/is not allowed. + -
+
shellis the desired shell for the user. If set to-, then +/bin/falseis set as the userâs shell. + -
+
groupsis the comma-separated list of additional groups the user + should be part of. If set to-, then the user will be a member of + no additional group. Missing groups will be created with an arbitrary +gid. + -
+
comment(aka GECOS + field) is an almost-free-form text. +
There are a few restrictions on the content of each field:
-
+except for
comment, all fields are mandatory. + -
+except for
comment, fields may not contain spaces. + -
+no field may contain a colon (
:). +
If home is not -, then the home directory, and all files below,
+will belong to the user and its main group.
Examples:
foo -1 bar -1 !=blabla /home/foo /bin/sh alpha,bravo Foo user
This will create this user:
-
+
username(aka login name) is:foo+ -
+
uidis computed by Buildroot + -
+main
groupis:bar+ -
+main group
gidis computed by Buildroot + -
+clear-text
passwordis:blabla, will be crypt(3)-encoded, and login is disabled. + -
+
homeis:/home/foo+ -
+
shellis:/bin/sh+ -
+
foois also a member ofgroups:alphaandbravo+ -
+
commentis:Foo user+
test 8000 wheel -1 = - /bin/sh - Test user
This will create this user:
-
+
username(aka login name) is:test+ -
+
uidis :8000+ -
+main
groupis:wheel+ -
+main group
gidis computed by Buildroot, and will use the value defined in the rootfs skeleton + -
+
passwordis empty (aka no password). + -
+
homeis/but will not belong totest+ -
+
shellis:/bin/sh+ -
+
testis not a member of any additionalgroups+ -
+
commentis:Test user+
| Packages | Target packages â ⦠|
|---|---|
a10disp | â Hardware handling |
acl | â System tools |
acpid | â Hardware handling |
adwaita icon theme | â Fonts, icons, sounds and themes |
aespipe | â Miscellaneous |
agent++ | â Libraries â Networking |
aiccu | â Networking applications |
aircrack-ng | â Networking applications |
alsa-lib | â Libraries â Audio/Sound |
alsa-utils | â Audio and video applications |
alsamixergui | â Graphic libraries and applications (graphic/text) |
am335x-pru-package | â Hardware handling |
am33x-cm3 | â Hardware handling â Firmware |
apache | â Networking applications |
apitrace | â Graphic libraries and applications (graphic/text) |
applewmproto | â Graphic libraries and applications (graphic/text) â X11R7 X protocols |
appres | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
apr | â Libraries â Other |
apr-util | â Libraries â Other |
argp-standalone | â Libraries â Other |
argus | â Networking applications |
armadillo | â Libraries â Other |
arptables | â Networking applications |
at | â Shell and utilities |
atftp | â Networking applications |
atk | â Libraries â Graphics |
attr | â System tools |
audiofile | â Libraries â Audio/Sound |
aumix | â Audio and video applications |
autossh | â Networking applications |
avahi | â Networking applications |
avrdude | â Hardware handling |
axel | â Networking applications |
b43-firmware | â Hardware handling â Firmware |
bandwidthd | â Networking applications |
bash | â Shell and utilities |
batctl | â Networking applications |
bc | â Miscellaneous |
bcache tools | â Hardware handling |
bcusdk | â Networking applications |
bdftopcf | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
bdwgc | â Libraries â Other |
beecrypt | â Libraries â Crypto |
beforelight | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
bellagio | â Audio and video applications |
benejson | â Libraries â JSON/XML |
berkeleydb | â Libraries â Database |
bigreqsproto | â Graphic libraries and applications (graphic/text) â X11R7 X protocols |
bind | â Networking applications |
binutils | â Development tools |
biosdevname | â Hardware handling |
bitmap | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
Bitstream Vera | â Fonts, icons, sounds and themes |
blackbox (deprecated) | â Graphic libraries and applications (graphic/text) |
blktrace | â Debugging, profiling and benchmark |
bluez-utils | â Networking applications |
bluez-utils 5.x | â Networking applications |
bmon | â Networking applications |
boa | â Networking applications |
bonnie++ | â Debugging, profiling and benchmark |
boost | â Libraries â Other |
bootstrap | â Libraries â Javascript |
bootutils | â System tools |
botan | â Libraries â Crypto |
bridge-utils | â Networking applications |
bsdiff | â Development tools |
btrfs-progs | â Filesystem and flash utilities |
bullet | â Libraries â Graphics |
bustle | â Development tools |
BusyBox | |
bwm-ng | â Networking applications |
bzip2 | â Compressors and decompressors |
c-ares | â Libraries â Networking |
c-periphery | â Libraries â Hardware handling |
CA Certificates | â Libraries â Crypto |
cache-calibrator | â Debugging, profiling and benchmark |
cairo | â Libraries â Graphics |
can-utils | â Networking applications |
canfestival | â Libraries â Networking |
cblas/clapack | â Libraries â Other |
cc-tool | â Hardware handling |
ccid | â Libraries â Hardware handling |
ccrypt | â Shell and utilities |
cdrkit | â Hardware handling |
cegui06 | â Graphic libraries and applications (graphic/text) |
celt051 | â Libraries â Audio/Sound |
cgic | â Libraries â Networking |
cgilua | â Interpreter languages and scripting â Lua libraries/modules |
chrony | â Networking applications |
cifs-utils | â Filesystem and flash utilities |
civetweb | â Networking applications |
cJSON | â Libraries â JSON/XML |
clamav | â Miscellaneous |
classpath | â Libraries â Other |
collectd | â Miscellaneous |
compositeproto | â Graphic libraries and applications (graphic/text) â X11R7 X protocols |
connman | â Networking applications |
conntrack-tools | â Networking applications |
copas | â Interpreter languages and scripting â Lua libraries/modules |
coreutils | â System tools |
cosmo | â Interpreter languages and scripting â Lua libraries/modules |
coxpcall | â Interpreter languages and scripting â Lua libraries/modules |
cppcms | â Libraries â Other |
cppdb | â Libraries â Database |
cppunit | â Development tools |
cppzmq | â Libraries â Networking |
cpuload | â System tools |
cramfs | â Filesystem and flash utilities |
crda | â Networking applications |
cryptodev-linux | â Libraries â Crypto â cryptodev variant |
cryptsetup | â Hardware handling |
ctorrent | â Networking applications |
cups (deprecated) | â Networking applications |
curlftpfs (FUSE) | â Filesystem and flash utilities |
cvs | â Development tools |
cwiid | â Hardware handling |
czmq | â Libraries â Networking |
dado | â Interpreter languages and scripting â Lua libraries/modules |
damageproto | â Graphic libraries and applications (graphic/text) â X11R7 X protocols |
dash | â Shell and utilities |
dbus | â Hardware handling |
dbus-c++ | â Hardware handling |
dbus-glib | â Hardware handling |
dbus-python | â Hardware handling |
dbus-triggerd | â Hardware handling |
dcron | â System tools |
debianutils | â System tools |
Declarative module | â Graphic libraries and applications (graphic/text) |
DejaVu fonts | â Fonts, icons, sounds and themes |
devmem2 | â Hardware handling |
dhcp (ISC) | â Networking applications |
dhcpcd | â Networking applications |
dhcpdump | â Networking applications |
dhrystone | â Debugging, profiling and benchmark |
dialog | â Shell and utilities |
diffutils | â Development tools |
dillo | â Graphic libraries and applications (graphic/text) |
ding-libs | â Libraries â Other |
directfb | â Graphic libraries and applications (graphic/text) |
directfb examples | â Graphic libraries and applications (graphic/text) |
directfb virtual input extension | â Graphic libraries and applications (graphic/text) |
dmalloc | â Debugging, profiling and benchmark |
dmidecode | â Hardware handling |
dmraid | â Hardware handling |
dmxproto | â Graphic libraries and applications (graphic/text) â X11R7 X protocols |
dnsmasq | â Networking applications |
docker | â Graphic libraries and applications (graphic/text) |
dosfstools | â Filesystem and flash utilities |
dovecot | â Mail |
dovecot-pigeonhole | â Mail |
drbd-utils | â Networking applications |
dri2proto | â Graphic libraries and applications (graphic/text) â X11R7 X protocols |
dri3proto | â Graphic libraries and applications (graphic/text) â X11R7 X protocols |
dropbear | â Networking applications |
dropwatch | â Debugging, profiling and benchmark |
dsp-tools | â System tools |
dstat | â Debugging, profiling and benchmark |
dtach | â Shell and utilities |
dtc (libfdt) | â Libraries â Hardware handling |
dtv-scan-tables | â Hardware handling |
duma | â Debugging, profiling and benchmark |
dvb-apps | â Hardware handling |
dvbsnoop | â Hardware handling |
dvdauthor | â Audio and video applications |
dvdrw-tools | â Audio and video applications |
e2fsprogs | â Filesystem and flash utilities |
e2tools | â Filesystem and flash utilities |
ebtables | â Networking applications |
ecryptfs-utils | â Filesystem and flash utilities |
ed | â Text editors and viewers |
editres | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
eeprog | â Hardware handling |
eigen | â Libraries â Other |
ejabberd | â Networking applications |
elfutils | â Libraries â Other |
empty | â Miscellaneous |
enchant | â Libraries â Text and terminal handling |
encodings | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
enlightenment | â Graphic libraries and applications (graphic/text) |
Enlightenment Foundation Libraries | â Graphic libraries and applications (graphic/text) |
enscript | â Interpreter languages and scripting |
epoxy | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
erlang | â Interpreter languages and scripting |
erlang-goldrush | â Interpreter languages and scripting â Erlang libraries/modules |
erlang-lager | â Interpreter languages and scripting â Erlang libraries/modules |
erlang-p1-cache-tab | â Interpreter languages and scripting â Erlang libraries/modules |
erlang-p1-iconv | â Interpreter languages and scripting â Erlang libraries/modules |
erlang-p1-sip | â Interpreter languages and scripting â Erlang libraries/modules |
erlang-p1-stringprep | â Interpreter languages and scripting â Erlang libraries/modules |
erlang-p1-stun | â Interpreter languages and scripting â Erlang libraries/modules |
erlang-p1-tls | â Interpreter languages and scripting â Erlang libraries/modules |
erlang-p1-utils | â Interpreter languages and scripting â Erlang libraries/modules |
erlang-p1-xml | â Interpreter languages and scripting â Erlang libraries/modules |
erlang-p1-yaml | â Interpreter languages and scripting â Erlang libraries/modules |
erlang-p1-zlib | â Interpreter languages and scripting â Erlang libraries/modules |
espeak | â Audio and video applications |
ethtool | â Networking applications |
eudev | â Hardware handling |
evemu | â Hardware handling |
evtest | â Hardware handling |
exFAT (FUSE) | â Filesystem and flash utilities |
exfat-utils | â Filesystem and flash utilities |
exim | â Mail |
exiv2 | â Libraries â Graphics |
expat | â Libraries â JSON/XML |
expect | â Interpreter languages and scripting â tcl libraries/modules |
expedite | â Graphic libraries and applications (graphic/text) |
explorercanvas | â Libraries â Javascript |
ezxml | â Libraries â JSON/XML |
f2fs-tools | â Filesystem and flash utilities |
faad2 | â Audio and video applications |
faifa | â Networking applications |
fan-ctrl | â Hardware handling |
fb-test-app | â Graphic libraries and applications (graphic/text) |
fbdump (Framebuffer Capture Tool) | â Graphic libraries and applications (graphic/text) |
fbgrab | â Graphic libraries and applications (graphic/text) |
fbset | â Graphic libraries and applications (graphic/text) |
fbterm | â Graphic libraries and applications (graphic/text) |
fbv | â Graphic libraries and applications (graphic/text) |
fconfig | â Hardware handling |
fdk-aac | â Libraries â Audio/Sound |
feh | â Graphic libraries and applications (graphic/text) |
fetchmail | â Mail |
ffmpeg | â Audio and video applications |
fftw | â Libraries â Other |
file | â Shell and utilities |
filemq | â Libraries â Networking |
findutils | â Development tools |
fio | â Debugging, profiling and benchmark |
firmware-imx | â Hardware handling |
fis | â Hardware handling |
fixesproto | â Graphic libraries and applications (graphic/text) â X11R7 X protocols |
flac | â Audio and video applications |
flann | â Libraries â Other |
flashbench | â Filesystem and flash utilities |
flashrom | â Hardware handling |
flex | â Development tools |
flickcurl | â Libraries â Networking |
flite | â Audio and video applications |
flot | â Libraries â Javascript |
fltk | â Libraries â Graphics |
fluxbox | â Graphic libraries and applications (graphic/text) |
fmc | â Networking applications |
fmlib | â Libraries â Networking |
fmtools | â Hardware handling |
font-adobe-100dpi | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-adobe-75dpi | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-adobe-utopia-100dpi | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-adobe-utopia-75dpi | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-adobe-utopia-type1 | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-alias | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-arabic-misc | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-bh-100dpi | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-bh-75dpi | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-bh-lucidatypewriter-100dpi | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-bh-lucidatypewriter-75dpi | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-bh-ttf | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-bh-type1 | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-bitstream-100dpi | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-bitstream-75dpi | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-bitstream-type1 | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-cronyx-cyrillic | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-cursor-misc | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-daewoo-misc | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-dec-misc | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-ibm-type1 | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-isas-misc | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-jis-misc | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-micro-misc | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-misc-cyrillic | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-misc-ethiopic | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-misc-meltho | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-misc-misc | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-mutt-misc | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-schumacher-misc | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-screen-cyrillic | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-sony-misc | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-sun-misc | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-util | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-winitzki-cyrillic | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
font-xfree86-type1 | â Graphic libraries and applications (graphic/text) â X11R7 Fonts |
fontcacheproto | â Graphic libraries and applications (graphic/text) â X11R7 X protocols |
fontconfig | â Libraries â Graphics |
fontsproto | â Graphic libraries and applications (graphic/text) â X11R7 X protocols |
fonttosfnt | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
foomatic_filters (deprecated) | â Networking applications |
fping | â Networking applications |
freeradius-client | â Libraries â Networking |
freerdp | â Graphic libraries and applications (graphic/text) |
Freescale i.MX libraries | â Hardware handling |
freetype | â Libraries â Graphics |
fslsfonts | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
fstobdf | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
fswebcam | â Graphic libraries and applications (graphic/text) |
ftop | â System tools |
fxload | â Hardware handling |
gadgetfs-test | â Hardware handling |
gamin | â Libraries â Filesystem |
gawk | â Development tools |
gd | â Libraries â Graphics |
gdb | â Debugging, profiling and benchmark |
gdbm | â Libraries â Database |
gdk-pixbuf | â Libraries â Graphics |
genext2fs | â Filesystem and flash utilities |
genpart | â Filesystem and flash utilities |
genromfs | â Filesystem and flash utilities |
geoip | â Libraries â Networking |
gesftpserver | â Networking applications |
getent | â System tools |
gettext | â Development tools |
ghostscript-fonts | â Fonts, icons, sounds and themes |
giblib | â Libraries â Graphics |
giflib | â Libraries â Graphics |
git | â Development tools |
glib-networking | â Libraries â Networking |
glibmm | â Libraries â Other |
glm | â Libraries â Other |
glmark2 | â Graphic libraries and applications (graphic/text) |
glproto | â Graphic libraries and applications (graphic/text) â X11R7 X protocols |
gmp | â Libraries â Other |
gmpc | â Graphic libraries and applications (graphic/text) |
gnu-efi | â Libraries â Hardware handling |
gnuchess | â Games |
gnupg | â Shell and utilities |
gnupg2 | â Shell and utilities |
gnuplot | â Graphic libraries and applications (graphic/text) |
gnuradio | â Miscellaneous |
gnutls | â Libraries â Crypto |
Google font directory | â Miscellaneous |
google-breakpad | â Debugging, profiling and benchmark |
gperf | â Development tools |
gpm | â Hardware handling |
gpsd | â Hardware handling |
gptfdisk | â Hardware handling |
gpu-amd-bin-mx51 (also imx53) | â Hardware handling |
gpu-viv-bin-mx6q | â Hardware handling |
gqview | â Graphic libraries and applications (graphic/text) |
grantlee | â Graphic libraries and applications (graphic/text) |
grep | â Development tools |
gsl | â Libraries â Other |
gst-dsp | â Audio and video applications |
gst-ffmpeg | â Audio and video applications |
gst-fsl-plugins | â Audio and video applications |
gst-omapfb | â Audio and video applications |
gst-omx | â Audio and video applications |
gst-plugin-x170 | â Audio and video applications |
gst-plugins-bad | â Audio and video applications |
gst-plugins-base | â Audio and video applications |
gst-plugins-good | â Audio and video applications |
gst-plugins-ugly | â Audio and video applications |
gst1-imx | â Audio and video applications |
gst1-libav | â Audio and video applications |
gst1-plugins-bad | â Audio and video applications |
gst1-plugins-base | â Audio and video applications |
gst1-plugins-good | â Audio and video applications |
gst1-plugins-ugly | â Audio and video applications |
gst1-validate | â Audio and video applications |
gstreamer 0.10 | â Audio and video applications |
gstreamer 1.x | â Audio and video applications |
gtest | â Libraries â Other |
gtk engines | â Fonts, icons, sounds and themes |
gtkperf (performance test for GTK2) | â Graphic libraries and applications (graphic/text) |
guile | â Interpreter languages and scripting |
gutenprint (deprecated) | â Networking applications |
gvfs | â Hardware handling |
gzip | â Compressors and decompressors |
hans | â Networking applications |
harfbuzz | â Libraries â Graphics |
haserl | â Interpreter languages and scripting |
haveged | â Miscellaneous |
hdparm | â Hardware handling |
heirloom-mailx | â Mail |
hiawatha | â Networking applications |
hicolor icon theme | â Fonts, icons, sounds and themes |
hostapd | â Networking applications |
hplip (deprecated) | â Networking applications |
htop | â System tools |
httping | â Networking applications |
hwdata | â Hardware handling |
hwloc | â Hardware handling |
i2c-tools | â Hardware handling |
iceauth | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
ico | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
icu | â Libraries â Text and terminal handling |
ifplugd | â Networking applications |
iftop | â Networking applications |
ifupdown | â Networking applications |
igh-ethercat | â Networking applications |
igmpproxy | â Networking applications |
ijs | â Libraries â Graphics |
imagemagick | â Graphic libraries and applications (graphic/text) |
imlib2 | â Libraries â Graphics |
imx-lib | â Hardware handling |
imx-vpu | â Hardware handling |
inadyn | â Networking applications |
inconsolata | â Fonts, icons, sounds and themes |
infozip | â Compressors and decompressors |
inotify-tools | â Shell and utilities |
input-event-daemon | â Hardware handling |
input-tools | â Hardware handling |
inputproto | â Graphic libraries and applications (graphic/text) â X11R7 X protocols |
intel-microcode | â Hardware handling |
intltool | â Development tools |
iodine | â Networking applications |
iostat | â Hardware handling |
iotop | â System tools |
iozone | â Debugging, profiling and benchmark |
iperf | â Networking applications |
iperf3 | â Networking applications |
ipkg | â Package managers |
ipmitool | â Hardware handling |
ipmiutil | â Hardware handling |
iproute2 | â Networking applications |
iprutils | â System tools |
ipsec-tools | â Networking applications |
ipset | â Networking applications |
iptables | â Networking applications |
iptraf-ng | â Networking applications |
iputils | â Networking applications |
irda-utils | â Hardware handling |
irqbalance | â System tools |
iucode-tool | â Hardware handling |
iw | â Networking applications |
jack2 | â Audio and video applications |
jamvm | â Interpreter languages and scripting |
jansson | â Libraries â JSON/XML |
janus-gateway | â Networking applications |
jasper | â Libraries â Graphics |
jhead | â Graphic libraries and applications (graphic/text) |
jimtcl | â Interpreter languages and scripting |
joe | â Text editors and viewers |
jpeg | â Libraries â Graphics â jpeg variant |
jpeg-turbo | â Libraries â Graphics â jpeg variant |
jq | â Development tools |
jQuery | â Libraries â Javascript |
jQuery keyboard | â Libraries â Javascript |
jQuery UI | â Libraries â Javascript |
jQuery UI themes | â Libraries â Javascript |
jquery-mobile | â Libraries â Javascript |
jQuery-Sparkline | â Libraries â Javascript |
jQuery-Validation | â Libraries â Javascript |
jsmin | â Libraries â Javascript |
json-c | â Libraries â JSON/XML |
json-glib | â Libraries â JSON/XML |
json-javascript | â Libraries â Javascript |
jsoncpp | â Libraries â JSON/XML |
kbd | â Hardware handling |
kbproto | â Graphic libraries and applications (graphic/text) â X11R7 X protocols |
kexec | â Debugging, profiling and benchmark |
kexec-lite | â Debugging, profiling and benchmark |
keyutils | â System tools |
kismet | â Networking applications |
kmod | â System tools |
knock | â Networking applications |
kobs-ng | â Filesystem and flash utilities |
kodi | â Audio and video applications |
kodi-addon-xvdr | â Audio and video applications |
kodi-audioencoder-flac | â Audio and video applications |
kodi-audioencoder-lame | â Audio and video applications |
kodi-audioencoder-vorbis | â Audio and video applications |
kodi-audioencoder-wav | â Audio and video applications |
kodi-pvr-addons | â Audio and video applications |
ktap | â Debugging, profiling and benchmark |
lame | â Audio and video applications |
latencytop | â Debugging, profiling and benchmark |
lbase64 | â Interpreter languages and scripting â Lua libraries/modules |
LBreakout2 | â Games |
lcdapi | â Libraries â Hardware handling |
lcdproc | â Hardware handling |
lcms2 | â Libraries â Graphics |
leafnode2 | â Networking applications |
leafpad | â Graphic libraries and applications (graphic/text) |
less | â Text editors and viewers |
lesstif | â Libraries â Graphics |
leveldb | â Libraries â Database |
lftp | â Networking applications |
libaio | â Libraries â Hardware handling |
libao | â Libraries â Audio/Sound |
libarchive | â Libraries â Compression and decompression |
libargtable2 | â Libraries â Other |
libart | â Libraries â Graphics |
libass | â Libraries â Multimedia |
libassuan | â Libraries â Crypto |
libatasmart | â Libraries â Hardware handling |
libatomic_ops | â Libraries â Other |
libbluray | â Libraries â Multimedia |
libbsd | â Libraries â Other |
libcap | â Libraries â Other |
libcap-ng | â Libraries â Other |
libcdaudio | â Libraries â Audio/Sound |
libcdio | â Libraries â Audio/Sound |
libcec | â Libraries â Hardware handling |
libcgi | â Libraries â Networking |
libcgicc | â Libraries â Networking |
libcgroup | â Libraries â Other |
libcli | â Libraries â Text and terminal handling |
libcofi | â Libraries â Other |
libconfig | â Libraries â Filesystem |
libconfuse | â Libraries â Filesystem |
libcue | â Libraries â Audio/Sound |
libcuefile | â Libraries â Audio/Sound |
libcurl | â Libraries â Networking |
libdaemon | â Libraries â Other |
libdcadec | â Libraries â Multimedia |
libdmtx | â Libraries â Graphics |
libdmx | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
libdnet | â Libraries â Networking |
libdri2 | â Libraries â Graphics |
libdrm | â Libraries â Graphics |
libdvbcsa | â Libraries â Multimedia |
libdvbsi | â Libraries â Multimedia |
libdvdnav | â Libraries â Multimedia |
libdvdread | â Libraries â Multimedia |
libebml | â Libraries â Multimedia |
libecore | â Graphic libraries and applications (graphic/text) |
libedbus | â Graphic libraries and applications (graphic/text) |
libedit | â Libraries â Text and terminal handling |
libedje | â Graphic libraries and applications (graphic/text) |
libee | â Libraries â Other |
libeet | â Graphic libraries and applications (graphic/text) |
libefreet | â Graphic libraries and applications (graphic/text) |
libeina | â Graphic libraries and applications (graphic/text) |
libeio | â Graphic libraries and applications (graphic/text) |
libelementary | â Graphic libraries and applications (graphic/text) |
libembryo | â Graphic libraries and applications (graphic/text) |
libenca | â Libraries â Text and terminal handling |
Liberation (Free fonts) | â Fonts, icons, sounds and themes |
libesmtp | â Mail |
libestr | â Libraries â Text and terminal handling |
libethumb | â Graphic libraries and applications (graphic/text) |
libev | â Libraries â Other |
libevas | â Graphic libraries and applications (graphic/text) |
libevas generic loaders | â Graphic libraries and applications (graphic/text) |
libevdev | â Libraries â Other |
libevent | â Libraries â Other |
libexif | â Libraries â Graphics |
libeXosip2 | â Libraries â Networking |
libfcgi | â Libraries â Networking |
libffi | â Libraries â Other |
libfontenc | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
libfreefare | â Libraries â Hardware handling |
libfreeimage | â Libraries â Graphics |
libfribidi | â Libraries â Text and terminal handling |
libFS | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
libfslcodec | â Libraries â Multimedia |
libfslparser | â Libraries â Multimedia |
libfslvpuwrap | â Libraries â Multimedia |
libftdi | â Libraries â Hardware handling |
libftdi1 | â Libraries â Hardware handling |
libfuse | â Libraries â Filesystem |
libgail | â Libraries â Graphics |
libgcrypt | â Libraries â Crypto |
libgeotiff | â Libraries â Graphics |
libglade | â Libraries â Graphics |
libglew | â Libraries â Graphics |
libglib2 | â Libraries â Other |
libglu | â Libraries â Graphics |
libgpg-error | â Libraries â Crypto |
libgpgme | â Libraries â Crypto |
libgsasl | â Libraries â Networking |
libgtk2 | â Libraries â Graphics |
libgtk3 | â Libraries â Graphics |
libhid | â Libraries â Hardware handling |
libical | â Libraries â Other |
libICE | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
libiconv | â Libraries â Text and terminal handling |
libid3tag | â Libraries â Audio/Sound |
libidn | â Libraries â Networking |
libiio | â Libraries â Hardware handling |
libinput | â Libraries â Hardware handling |
libiqrf | â Libraries â Hardware handling |
libiscsi | â Libraries â Networking |
libjson | â Libraries â JSON/XML |
libksba | â Libraries â Crypto |
liblinear | â Libraries â Other |
libllcp | â Libraries â Hardware handling |
liblo | â Libraries â Audio/Sound |
liblockfile | â Libraries â Filesystem |
liblog4c-localtime | â Libraries â Logging |
liblogging | â Libraries â Logging |
libmad | â Libraries â Audio/Sound |
libmatroska | â Libraries â Multimedia |
libmbim | â Libraries â Hardware handling |
libmbus | â Libraries â Networking |
libmcrypt | â Libraries â Crypto |
libmemcached | â Libraries â Networking |
libmhash | â Libraries â Crypto |
libmicrohttpd | â Libraries â Networking |
libmms | â Libraries â Multimedia |
libmnl | â Libraries â Networking |
libmodbus | â Libraries â Networking |
libmodplug | â Libraries â Audio/Sound |
libmpd | â Libraries â Audio/Sound |
libmpdclient | â Libraries â Audio/Sound |
libmpeg2 | â Libraries â Multimedia |
libndp | â Libraries â Networking |
libneon | â Libraries â Networking |
libnetfilter_acct | â Libraries â Networking |
libnetfilter_conntrack | â Libraries â Networking |
libnetfilter_cthelper | â Libraries â Networking |
libnetfilter_cttimeout | â Libraries â Networking |
libnetfilter_log | â Libraries â Networking |
libnetfilter_queue | â Libraries â Networking |
libnfc | â Libraries â Hardware handling |
libnfnetlink | â Libraries â Networking |
libnfs | â Libraries â Filesystem |
libnftnl | â Libraries â Networking |
libnice | â Libraries â Networking |
libnl | â Libraries â Networking |
libnspr | â Libraries â Other |
libnss | â Libraries â Crypto |
liboauth | â Libraries â Networking |
libogg | â Libraries â Multimedia |
liboping | â Libraries â Networking |
libosip2 | â Libraries â Networking |
libpcap | â Libraries â Networking |
libpciaccess | â Libraries â Hardware handling |
libpfm4 | â Libraries â Other |
libphidget | â Libraries â Hardware handling |
libplayer | â Libraries â Multimedia |
libplist | â Libraries â Other |
libpng | â Libraries â Graphics |
libpthread-stubs | â Libraries â Other |
libpthsem | â Libraries â Other |
libqmi | â Libraries â Hardware handling |
libqrencode | â Libraries â Graphics |
libraw | â Libraries â Graphics |
libraw1394 | â Libraries â Hardware handling |
libreplaygain | â Libraries â Audio/Sound |
librsvg | â Libraries â Graphics |
librsync | â Libraries â Networking |
librtlsdr | â Libraries â Hardware handling |
librtmp | â Libraries â Networking |
libsamplerate | â Libraries â Audio/Sound |
libseccomp | â Libraries â Other |
libsecret | â Libraries â Crypto |
libselinux | â Libraries â Security |
libsemanage | â Libraries â Security |
libsepol | â Libraries â Security |
libserial | â Libraries â Hardware handling |
libserialport | â Libraries â Hardware handling |
libsexy | â Graphic libraries and applications (graphic/text) |
libsha1 | â Libraries â Crypto |
libshairplay | â Libraries â Networking |
libshout | â Libraries â Networking |
libsidplay2 | â Libraries â Audio/Sound |
libsigc++ | â Libraries â Other |
libsigrok | â Libraries â Hardware handling |
libsigrokdecode | â Libraries â Hardware handling |
libsigsegv | â Libraries â Other |
libSM | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
libsndfile | â Libraries â Audio/Sound |
libsoc | â Libraries â Hardware handling |
libsocketcan | â Libraries â Networking |
libsoup | â Libraries â Networking |
libsoxr | â Libraries â Audio/Sound |
libsrtp | â Libraries â Networking |
libssh2 | â Libraries â Crypto |
libstrophe | â Libraries â Networking |
libsvg | â Libraries â Graphics |
libsvg-cairo | â Libraries â Graphics |
libsvgtiny | â Libraries â Graphics |
libsysfs | â Libraries â Filesystem |
libtasn1 | â Libraries â Other |
libtheora | â Libraries â Multimedia |
libtirpc | â Libraries â Networking |
libtool | â Development tools |
libtorrent | â Libraries â Networking |
libtpl | â Libraries â Other |
libubox | â Libraries â Other |
libuci | â Libraries â Other |
libungif (deprecated) | â Libraries â Graphics |
libunistring | â Libraries â Text and terminal handling |
libunwind | â Libraries â Other |
libupnp | â Libraries â Networking |
libupnpp | â Libraries â Networking |
liburcu | â Libraries â Other |
liburiparser | â Libraries â Networking |
libusb | â Libraries â Hardware handling |
libusb-compat | â Libraries â Hardware handling |
libuv | â Libraries â Other |
libv4l | â Libraries â Hardware handling |
libva | â Libraries â Graphics |
libva-intel-driver | â Libraries â Graphics |
libvips | â Libraries â Graphics |
libvncserver | â Libraries â Networking |
libvorbis | â Libraries â Audio/Sound |
libvpx | â Audio and video applications |
libwebsock | â Libraries â Networking |
libwebsockets | â Libraries â Networking |
libX11 | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
libXau | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
libXaw | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
libxcb | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
libXcomposite | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
libXcursor | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
libXdamage | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
libXdmcp | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
libXext | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
libXfixes | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
libXfont | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
libXft | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
libXi | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
libXinerama | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
libxkbcommon | â Libraries â Hardware handling |
libxkbfile | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
libxml++ | â Libraries â JSON/XML |
libxml2 | â Libraries â JSON/XML |
libxmlrpc | â Libraries â JSON/XML |
libXmu | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
libXpm | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
libXrandr | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
libXrender | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
libXres | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
libXScrnSaver | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
libxshmfence | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
libxslt | â Libraries â JSON/XML |
libXt | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
libXtst | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
libXv | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
libXvMC | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
libXxf86dga | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
libXxf86vm | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
libyaml | â Libraries â JSON/XML |
libz160 | â Hardware handling |
libzip | â Libraries â Compression and decompression |
lightning | â Libraries â Other |
lighttpd | â Networking applications |
linenoise | â Libraries â Text and terminal handling |
linknx | â Networking applications |
links | â Networking applications |
linphone | â Networking applications |
linux-firmware | â Hardware handling â Firmware |
linux-fusion communication layer for DirectFB multi | â Graphic libraries and applications (graphic/text) |
linux-pam | â Libraries â Other |
linux-zigbee | â Networking applications |
lirc-tools | â Hardware handling |
listres | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
LiTE (toolbox engine) | â Graphic libraries and applications (graphic/text) |
live555 | â Libraries â Multimedia |
ljlinenoise | â Interpreter languages and scripting â Lua libraries/modules |
ljsyscall | â Interpreter languages and scripting â Lua libraries/modules |
lm-sensors | â Hardware handling |
lmbench | â Debugging, profiling and benchmark |
lockdev | â Libraries â Filesystem |
lockfile programs | â Shell and utilities |
log4cplus | â Libraries â Logging |
log4cxx | â Libraries â Logging |
logrotate | â Shell and utilities |
logsurfer | â Shell and utilities |
lpeg | â Interpreter languages and scripting â Lua libraries/modules |
lpty | â Interpreter languages and scripting â Lua libraries/modules |
lrandom | â Interpreter languages and scripting â Lua libraries/modules |
lrzsz | â Networking applications |
lshw | â Hardware handling |
lsof | â Debugging, profiling and benchmark |
lsqlite3 | â Interpreter languages and scripting â Lua libraries/modules |
lsuio | â Hardware handling |
ltp-testsuite | â Debugging, profiling and benchmark |
ltrace | â Debugging, profiling and benchmark |
LTris | â Games |
lttng-babeltrace | â Debugging, profiling and benchmark |
lttng-libust | â Libraries â Other |
lttng-modules | â Debugging, profiling and benchmark |
lttng-tools | â Debugging, profiling and benchmark |
lua | â Interpreter languages and scripting |
lua-cjson | â Interpreter languages and scripting â Lua libraries/modules |
lua-coat | â Interpreter languages and scripting â Lua libraries/modules |
lua-coatpersistent | â Interpreter languages and scripting â Lua libraries/modules |
lua-csnappy | â Interpreter languages and scripting â Lua libraries/modules |
lua-ev | â Interpreter languages and scripting â Lua libraries/modules |
lua-messagepack | â Interpreter languages and scripting â Lua libraries/modules |
lua-msgpack-native | â Interpreter languages and scripting â Lua libraries/modules |
lua-periphery | â Interpreter languages and scripting â Lua libraries/modules |
lua-testmore | â Interpreter languages and scripting â Lua libraries/modules |
luabitop | â Interpreter languages and scripting â Lua libraries/modules |
luacrypto | â Interpreter languages and scripting â Lua libraries/modules |
luaexpat | â Interpreter languages and scripting â Lua libraries/modules |
luaexpatutils | â Interpreter languages and scripting â Lua libraries/modules |
luafilesystem | â Interpreter languages and scripting â Lua libraries/modules |
luajit | â Interpreter languages and scripting |
luajson | â Interpreter languages and scripting â Lua libraries/modules |
lualogging | â Interpreter languages and scripting â Lua libraries/modules |
luaposix | â Interpreter languages and scripting â Lua libraries/modules |
luasec | â Interpreter languages and scripting â Lua libraries/modules |
luasocket | â Interpreter languages and scripting â Lua libraries/modules |
luasql-sqlite3 | â Interpreter languages and scripting â Lua libraries/modules |
luit | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
lunit | â Interpreter languages and scripting â Lua libraries/modules |
lvm2 & device mapper | â Hardware handling |
lxc | â System tools |
lz4 | â Compressors and decompressors |
lzip | â Compressors and decompressors |
lzlib | â Interpreter languages and scripting â Lua libraries/modules |
lzo | â Libraries â Compression and decompression |
lzop | â Compressors and decompressors |
macchanger | â Networking applications |
madplay | â Audio and video applications |
make | â Development tools |
makedepend | â Graphic libraries and applications (graphic/text) â X11R7 Utilities |
makedevs | â Filesystem and flash utilities |
Matchbox Desktop | â Graphic libraries and applications (graphic/text) |
Matchbox Panel | â Graphic libraries and applications (graphic/text) |
Matchbox session common files | â Graphic libraries and applications (graphic/text) |
Matchbox Virtual Keyboard | â Graphic libraries and applications (graphic/text) |
MatchBox Window Manager | â Graphic libraries and applications (graphic/text) |
mc | â Text editors and viewers |
mcelog | â Debugging, profiling and benchmark |
mcookie | â Graphic libraries and applications (graphic/text) â X11R7 Utilities |
mcrypt | â Miscellaneous |
mdadm | â Hardware handling |
media-ctl | â Hardware handling |
mediastreamer | â Libraries â Multimedia |
memcached | â Networking applications |
memstat | â Debugging, profiling and benchmark |
memtest86 | â Hardware handling |
memtester | â Hardware handling |
mesa3d | â Graphic libraries and applications (graphic/text) |
mesa3d-demos | â Graphic libraries and applications (graphic/text) |
metacity | â Graphic libraries and applications (graphic/text) |
midori | â Graphic libraries and applications (graphic/text) |
mii-diag | â Networking applications |
Mini-XML | â Libraries â JSON/XML |
minicom | â Hardware handling |
minidlna | â Networking applications |
mjpegtools | â Audio and video applications |
mjpg-streamer | â Networking applications |
mkfontdir | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
mkfontscale | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
mmc-utils | â Filesystem and flash utilities |
mobile-broadband-provider-info | â Miscellaneous |
modemmanager | â Networking applications |
modplugtools | â Audio and video applications |
mongoose | â Networking applications |
mongrel2 | â Networking applications |
monit | â System tools |
mono | â Interpreter languages and scripting |
mosquitto | â Networking applications |
mp4v2 | â Libraries â Audio/Sound |
mpc | â Libraries â Other |
mpd | â Audio and video applications |
mpd-mpc | â Audio and video applications |
mpdecimal | â Libraries â Other |
mpfr | â Libraries â Other |
mpg123 | â Audio and video applications |
mplayer | â Audio and video applications |
mrouted | â Networking applications |
msgpack | â Libraries â Other |
msmtp | â Mail |
mtd, jffs2 and ubi/ubifs tools | â Filesystem and flash utilities |
mtdev | â Libraries â Hardware handling |
mtdev2tuio | â Libraries â Other |
mtools | â Filesystem and flash utilities |
mtr | â Networking applications |
Multimedia Module | â Graphic libraries and applications (graphic/text) |
musepack | â Audio and video applications |
mutt | â Mail |
MySQL | â Libraries â Database |
nano | â Text editors and viewers |
nanocom | â Hardware handling |
nbd | â Networking applications |
ncdu | â System tools |
ncftp | â Networking applications |
ncmpc | â Audio and video applications |
ncurses | â Libraries â Text and terminal handling |
ndisc6 tools | â Networking applications |
ne10 | â Libraries â Hardware handling |
neard | â Hardware handling |
neardal | â Libraries â Hardware handling |
net-tools | â Networking applications |
netatalk | â Networking applications |
netcat | â Networking applications |
netcat-openbsd | â Networking applications |
netperf | â Debugging, profiling and benchmark |
netplug | â Networking applications |
netsnmp | â Networking applications |
netstat-nat | â Networking applications |
nettle | â Libraries â Crypto |
networkmanager | â Networking applications |
newt | â Libraries â Text and terminal handling |
nfacct | â Networking applications |
nfs-utils | â Filesystem and flash utilities |
nftables | â Networking applications |
nginx | â Networking applications |
ngircd | â Networking applications |
ngrep | â Networking applications |
nmap | â Networking applications |
nodejs | â Interpreter languages and scripting |
noip | â Networking applications |
nss-mdns | â Libraries â Networking |
ntfs-3g | â Filesystem and flash utilities |
ntp | â Networking applications |
numactl | â System tools |
nut | â System tools |
nuttcp | â Networking applications |
nvidia-driver | â Hardware handling |
nvidia-tegra23 | â Hardware handling |
nvidia-tegra23 binaries | â Hardware handling |
nvidia-tegra23 codecs | â Hardware handling |
ocf-linux | â Libraries â Crypto â cryptodev variant |
oclock | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
ocrad | â Graphic libraries and applications (graphic/text) |
odhcp6c | â Networking applications |
odhcploc | â Networking applications |
ofono | â Hardware handling |
ola (open lighting architecture) | â Hardware handling |
olsrd | â Networking applications |
omniorb | â Libraries â Networking |
on2-8170-libs | â Audio and video applications |
on2-8170-modules | â Hardware handling |
open-plc-utils | â Networking applications |
open2300 | â Hardware handling |
opencore-amr | â Libraries â Audio/Sound |
opencv | â Libraries â Graphics |
openjpeg | â Libraries â Graphics |
openldap | â Libraries â Networking |
openntpd | â Networking applications |
openobex | â Networking applications |
openocd | â Hardware handling |
openpgm | â Libraries â Networking |
openpowerlink | â Hardware handling |
openssh | â Networking applications |
openssl | â Libraries â Crypto |
openswan | â Networking applications |
OpenTyrian | â Games |
OpenTyrian data | â Games |
openvmtools | â System tools |
openvpn | â Networking applications |
opkg | â Package managers |
oprofile | â Debugging, profiling and benchmark |
opus | â Libraries â Audio/Sound |
opus-tools | â Audio and video applications |
opusfile | â Libraries â Audio/Sound |
orbit | â Interpreter languages and scripting â Lua libraries/modules |
orc | â Libraries â Other |
oRTP | â Libraries â Networking |
owl-linux | â Hardware handling |
p11-kit | â Libraries â Other |
p910nd | â Networking applications |
pango | â Libraries â Graphics |
parted | â Hardware handling |
patch | â Development tools |
pax-utils | â Debugging, profiling and benchmark |
pciutils | â Hardware handling |
pcmanfm | â Graphic libraries and applications (graphic/text) |
pcre | â Libraries â Text and terminal handling |
pcsc-lite | â Libraries â Hardware handling |
perf | â Debugging, profiling and benchmark |
perl | â Interpreter languages and scripting |
perl-crypt-openssl-random | â Interpreter languages and scripting â Perl libraries/modules |
perl-crypt-openssl-rsa | â Interpreter languages and scripting â Perl libraries/modules |
perl-datetime-tiny | â Interpreter languages and scripting â Perl libraries/modules |
perl-db-file | â Interpreter languages and scripting â Perl libraries/modules |
perl-digest-hmac | â Interpreter languages and scripting â Perl libraries/modules |
perl-digest-sha1 | â Interpreter languages and scripting â Perl libraries/modules |
perl-encode-detect | â Interpreter languages and scripting â Perl libraries/modules |
perl-encode-locale | â Interpreter languages and scripting â Perl libraries/modules |
perl-file-listing | â Interpreter languages and scripting â Perl libraries/modules |
perl-file-util | â Interpreter languages and scripting â Perl libraries/modules |
perl-gd | â Interpreter languages and scripting â Perl libraries/modules |
perl-gdgraph | â Interpreter languages and scripting â Perl libraries/modules |
perl-gdtextutil | â Interpreter languages and scripting â Perl libraries/modules |
perl-html-parser | â Interpreter languages and scripting â Perl libraries/modules |
perl-html-tagset | â Interpreter languages and scripting â Perl libraries/modules |
perl-http-cookies | â Interpreter languages and scripting â Perl libraries/modules |
perl-http-daemon | â Interpreter languages and scripting â Perl libraries/modules |
perl-http-date | â Interpreter languages and scripting â Perl libraries/modules |
perl-http-message | â Interpreter languages and scripting â Perl libraries/modules |
perl-http-negotiate | â Interpreter languages and scripting â Perl libraries/modules |
perl-io-html | â Interpreter languages and scripting â Perl libraries/modules |
perl-io-socket-ssl | â Interpreter languages and scripting â Perl libraries/modules |
perl-json-tiny | â Interpreter languages and scripting â Perl libraries/modules |
perl-libwww-perl | â Interpreter languages and scripting â Perl libraries/modules |
perl-lwp-mediatypes | â Interpreter languages and scripting â Perl libraries/modules |
perl-mail-dkim | â Interpreter languages and scripting â Perl libraries/modules |
perl-mailtools | â Interpreter languages and scripting â Perl libraries/modules |
perl-mime-base64 | â Interpreter languages and scripting â Perl libraries/modules |
perl-mojolicious | â Interpreter languages and scripting â Perl libraries/modules |
perl-net-dns | â Interpreter languages and scripting â Perl libraries/modules |
perl-net-http | â Interpreter languages and scripting â Perl libraries/modules |
perl-net-ssleay | â Interpreter languages and scripting â Perl libraries/modules |
perl-netaddr-ip | â Interpreter languages and scripting â Perl libraries/modules |
perl-path-tiny | â Interpreter languages and scripting â Perl libraries/modules |
perl-time-hires | â Interpreter languages and scripting â Perl libraries/modules |
perl-timedate | â Interpreter languages and scripting â Perl libraries/modules |
perl-try-tiny | â Interpreter languages and scripting â Perl libraries/modules |
perl-uri | â Interpreter languages and scripting â Perl libraries/modules |
perl-www-robotrules | â Interpreter languages and scripting â Perl libraries/modules |
perl-xml-libxml | â Interpreter languages and scripting â Perl libraries/modules |
perl-xml-namespacesupport | â Interpreter languages and scripting â Perl libraries/modules |
perl-xml-sax | â Interpreter languages and scripting â Perl libraries/modules |
perl-xml-sax-base | â Interpreter languages and scripting â Perl libraries/modules |
phidgetwebservice | â Networking applications |
php | â Interpreter languages and scripting |
php-geoip | â Interpreter languages and scripting â External php extensions |
php-gnupg | â Interpreter languages and scripting â External php extensions |
php-imagick | â Interpreter languages and scripting â External php extensions |
php-memcached | â Interpreter languages and scripting â External php extensions |
php-ssh2 | â Interpreter languages and scripting â External php extensions |
php-yaml | â Interpreter languages and scripting â External php extensions |
php-zmq | â Interpreter languages and scripting â External php extensions |
picocom | â Hardware handling |
pifmrds | â Hardware handling |
pinentry | â Shell and utilities |
pixman | â Libraries â Graphics |
pkgconf | â Development tools |
poco | â Libraries â Other |
polarssl | â Libraries â Crypto |
polkit | â System tools |
poppler | â Libraries â Graphics |
popt | â Libraries â Text and terminal handling |
portaudio | â Libraries â Audio/Sound |
portmap | â Networking applications |
postgresql | â Libraries â Database |
powerpc-utils | â System tools |
powertop | â Hardware handling |
pppd | â Networking applications |
pps-tools | â Hardware handling |
pptp-linux | â Networking applications |
prboom | â Games |
presentproto | â Graphic libraries and applications (graphic/text) â X11R7 X protocols |
procps-ng | â System tools |
proftpd | â Networking applications |
protobuf | â Libraries â Other |
protobuf-c | â Libraries â Other |
proxychains-ng | â Networking applications |
psmisc | â System tools |
psplash | â Graphic libraries and applications (graphic/text) |
ptpd | â Networking applications |
ptpd2 | â Networking applications |
pulseaudio | â Audio and video applications |
pulseview | â Hardware handling |
pure-ftpd | â Networking applications |
pv | â Debugging, profiling and benchmark |
pwgen | â System tools |
python | â Interpreter languages and scripting |
python-alsaaudio | â Interpreter languages and scripting â external python modules |
python-bottle | â Interpreter languages and scripting â external python modules |
python-certifi | â Interpreter languages and scripting â external python modules |
python-cffi | â Interpreter languages and scripting â external python modules |
python-cheetah | â Interpreter languages and scripting â external python modules |
python-cherrypy | â Interpreter languages and scripting â external python modules |
python-coherence | â Interpreter languages and scripting â external python modules |
python-configobj | â Interpreter languages and scripting â external python modules |
python-configshell-fb | â Interpreter languages and scripting â external python modules |
python-crc16 | â Interpreter languages and scripting â external python modules |
python-daemon | â Interpreter languages and scripting â external python modules |
python-dialog | â Interpreter languages and scripting â external python modules |
python-django | â Interpreter languages and scripting â external python modules |
python-docopt | â Interpreter languages and scripting â external python modules |
python-dpkt | â Interpreter languages and scripting â external python modules |
python-enum | â Interpreter languages and scripting â external python modules |
python-enum34 | â Interpreter languages and scripting â external python modules |
python-flask | â Interpreter languages and scripting â external python modules |
python-flup | â Interpreter languages and scripting â external python modules |
python-gobject | â Interpreter languages and scripting â external python modules |
python-httplib2 | â Interpreter languages and scripting â external python modules |
python-id3 | â Interpreter languages and scripting â external python modules |
python-ipaddr | â Interpreter languages and scripting â external python modules |
python-ipy | â Interpreter languages and scripting â external python modules |
python-ipython | â Interpreter languages and scripting â external python modules |
python-itsdangerous | â Interpreter languages and scripting â external python modules |
python-jinja2 | â Interpreter languages and scripting â external python modules |
python-json-schema-validator | â Interpreter languages and scripting â external python modules |
python-keyring | â Interpreter languages and scripting â external python modules |
python-libconfig | â Interpreter languages and scripting â external python modules |
python-lxml | â Interpreter languages and scripting â external python modules |
python-mad | â Interpreter languages and scripting â external python modules |
python-mako | â Interpreter languages and scripting â external python modules |
python-markdown | â Interpreter languages and scripting â external python modules |
python-markupsafe | â Interpreter languages and scripting â external python modules |
python-meld3 | â Interpreter languages and scripting â external python modules |
python-msgpack | â Interpreter languages and scripting â external python modules |
python-netifaces | â Interpreter languages and scripting â external python modules |
python-networkmanager | â Interpreter languages and scripting â external python modules |
python-nfc | â Interpreter languages and scripting â external python modules |
python-numpy | â Interpreter languages and scripting â external python modules |
python-pam | â Interpreter languages and scripting â external python modules |
python-posix-ipc | â Interpreter languages and scripting â external python modules |
python-protobuf | â Interpreter languages and scripting â external python modules |
python-psutil | â Interpreter languages and scripting â external python modules |
python-pyasn | â Interpreter languages and scripting â external python modules |
python-pycrypto | â Interpreter languages and scripting â external python modules |
python-pyftpdlib | â Interpreter languages and scripting â external python modules |
python-pygame | â Interpreter languages and scripting â external python modules |
python-pyinotify | â Interpreter languages and scripting â external python modules |
python-pyparsing | â Interpreter languages and scripting â external python modules |
python-pypcap | â Interpreter languages and scripting â external python modules |
python-pyqt | â Interpreter languages and scripting â external python modules |
python-pyro | â Interpreter languages and scripting â external python modules |
python-pysendfile | â Interpreter languages and scripting â external python modules |
python-pysnmp | â Interpreter languages and scripting â external python modules |
python-pysnmp-apps | â Interpreter languages and scripting â external python modules |
python-pysnmp-mibs | â Interpreter languages and scripting â external python modules |
python-pyusb | â Interpreter languages and scripting â external python modules |
python-pyxb | â Interpreter languages and scripting â external python modules |
python-pyzmq | â Interpreter languages and scripting â external python modules |
python-requests | â Interpreter languages and scripting â external python modules |
python-rtslib-fb | â Interpreter languages and scripting â external python modules |
python-serial | â Interpreter languages and scripting â external python modules |
python-setuptools | â Interpreter languages and scripting â external python modules |
python-simplejson | â Interpreter languages and scripting â external python modules |
python-sip | â Interpreter languages and scripting â external python modules |
python-six | â Interpreter languages and scripting â external python modules |
python-spidev | â Interpreter languages and scripting â external python modules |
python-thrift | â Interpreter languages and scripting â external python modules |
python-tornado | â Interpreter languages and scripting â external python modules |
python-twisted | â Interpreter languages and scripting â external python modules |
python-urwid | â Interpreter languages and scripting â external python modules |
python-versiontools | â Interpreter languages and scripting â external python modules |
python-webpy | â Interpreter languages and scripting â external python modules |
python-werkzeug | â Interpreter languages and scripting â external python modules |
python-ws4py | â Interpreter languages and scripting â external python modules |
python-zope-interface | â Interpreter languages and scripting â external python modules |
python3 | â Interpreter languages and scripting |
qdecoder | â Libraries â Networking |
QEMU | â Miscellaneous |
qextserialport | â Graphic libraries and applications (graphic/text) |
qhull | â Libraries â Other |
qjson | â Graphic libraries and applications (graphic/text) |
qlibc | â Libraries â Other |
qpdf | â Miscellaneous |
Qt | â Graphic libraries and applications (graphic/text) |
qt-webkit-kiosk | â Graphic libraries and applications (graphic/text) |
Qt5 | â Graphic libraries and applications (graphic/text) |
qt5base | â Graphic libraries and applications (graphic/text) |
qt5cinex | â Graphic libraries and applications (graphic/text) |
qt5connectivity | â Graphic libraries and applications (graphic/text) |
qt5declarative | â Graphic libraries and applications (graphic/text) |
qt5enginio | â Graphic libraries and applications (graphic/text) |
qt5graphicaleffects | â Graphic libraries and applications (graphic/text) |
qt5imageformats | â Graphic libraries and applications (graphic/text) |
qt5multimedia | â Graphic libraries and applications (graphic/text) |
qt5quick1 | â Graphic libraries and applications (graphic/text) |
qt5quickcontrols | â Graphic libraries and applications (graphic/text) |
qt5script | â Graphic libraries and applications (graphic/text) |
qt5sensors | â Graphic libraries and applications (graphic/text) |
qt5serialport | â Graphic libraries and applications (graphic/text) |
qt5svg | â Graphic libraries and applications (graphic/text) |
qt5webkit | â Graphic libraries and applications (graphic/text) |
qt5webkit examples | â Graphic libraries and applications (graphic/text) |
qt5websockets | â Graphic libraries and applications (graphic/text) |
qt5x11extras | â Graphic libraries and applications (graphic/text) |
qt5xmlpatterns | â Graphic libraries and applications (graphic/text) |
qtuio | â Graphic libraries and applications (graphic/text) |
quagga | â Networking applications |
quota | â System tools |
qwt | â Graphic libraries and applications (graphic/text) |
radvd | â Networking applications |
ramspeed | â Debugging, profiling and benchmark |
ramspeed/smp | â Debugging, profiling and benchmark |
randrproto | â Graphic libraries and applications (graphic/text) â X11R7 X protocols |
rapidjson | â Libraries â JSON/XML |
rdesktop | â Graphic libraries and applications (graphic/text) |
read-edid | â Hardware handling |
readline | â Libraries â Text and terminal handling |
recordproto | â Graphic libraries and applications (graphic/text) â X11R7 X protocols |
redis | â Libraries â Database |
renderproto | â Graphic libraries and applications (graphic/text) â X11R7 X protocols |
resourceproto | â Graphic libraries and applications (graphic/text) â X11R7 X protocols |
rgb | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
rings | â Interpreter languages and scripting â Lua libraries/modules |
rng-tools | â Hardware handling |
roxml | â Libraries â JSON/XML |
rp-pppoe | â Networking applications |
rpcbind | â Networking applications |
rpi-firmware | â Hardware handling â Firmware |
rpi-userland | â Hardware handling |
rpm | â Package managers |
rrdtool | â Graphic libraries and applications (graphic/text) |
rsh-redone | â Networking applications |
rstart | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
rsync | â Networking applications |
rsyslog | â System tools |
rt-tests | â Debugging, profiling and benchmark |
rtai | â Real-Time |
rtorrent | â Networking applications |
rtptools | â Networking applications |
rubix | â Games |
ruby | â Interpreter languages and scripting |
samba (deprecated) | â Networking applications |
samba4 | â Networking applications |
sane-backends | â Hardware handling |
SawMan (Window Manager) | â Graphic libraries and applications (graphic/text) |
schifra | â Libraries â Other |
sconeserver | â Networking applications |
screen | â Shell and utilities |
Script Module | â Graphic libraries and applications (graphic/text) |
scripts | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
scrnsaverproto | â Graphic libraries and applications (graphic/text) â X11R7 X protocols |
SDL | â Graphic libraries and applications (graphic/text) |
SDL_gfx | â Graphic libraries and applications (graphic/text) |
SDL_image | â Graphic libraries and applications (graphic/text) |
SDL_mixer | â Graphic libraries and applications (graphic/text) |
SDL_net | â Graphic libraries and applications (graphic/text) |
SDL_sound | â Graphic libraries and applications (graphic/text) |
SDL_TTF | â Graphic libraries and applications (graphic/text) |
sdparm | â Hardware handling |
sed | â Development tools |
ser2net | â Networking applications |
sessreg | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
setserial | â Hardware handling |
setxkbmap | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
sg3-utils | â Hardware handling |
shairport-sync | â Networking applications |
shared-mime-info | â Miscellaneous |
shareware Doom WAD file | â Games |
showfont | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
sigrok-cli | â Hardware handling |
simicsfs | â Filesystem and flash utilities |
sispmctl | â Hardware handling |
sl | â Games |
slang | â Libraries â Text and terminal handling |
slirp | â Libraries â Networking |
smack | â System tools |
smartmontools | â Hardware handling |
smcroute | â Networking applications |
smproxy | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
smstools3 | â Hardware handling |
snappy | â Libraries â Compression and decompression |
snmp++ | â Libraries â Networking |
snowball-hdmiservice | â Hardware handling |
snowball-init | â Miscellaneous |
socat | â Networking applications |
socketcand | â Networking applications |
sofia-sip | â Libraries â Networking |
softether | â Networking applications |
sound-theme-borealis | â Fonts, icons, sounds and themes |
sound-theme-freedesktop | â Fonts, icons, sounds and themes |
sox | â Audio and video applications |
spawn-fcgi | â Networking applications |
speex | â Libraries â Audio/Sound |
spice protocol | â Networking applications |
spice server | â Networking applications |
spidev_test | â Debugging, profiling and benchmark |
sqlcipher | â Libraries â Database |
sqlite | â Libraries â Database |
squashfs | â Filesystem and flash utilities |
squid | â Networking applications |
sredird | â Hardware handling |
sshfs (FUSE) | â Filesystem and flash utilities |
sshpass | â Networking applications |
sstrip | â Development tools |
start-stop-daemon | â System tools |
startup-notification | â Libraries â Other |
statserial | â Hardware handling |
strace | â Debugging, profiling and benchmark |
stress | â Debugging, profiling and benchmark |
strongswan | â Networking applications |
stunnel | â Networking applications |
subversion | â Development tools |
sudo | â Shell and utilities |
sunxi nand-part | â Filesystem and flash utilities |
sunxi script.bin board file | â Hardware handling â Firmware |
sunxi-cedarx | â Hardware handling |
sunxi-mali | â Hardware handling |
supervisor | â System tools |
SVG Module | â Graphic libraries and applications (graphic/text) |
sylpheed | â Mail |
synergy | â Graphic libraries and applications (graphic/text) |
sysdig | â Debugging, profiling and benchmark |
syslogd & klogd | â System tools |
sysprof | â Debugging, profiling and benchmark |
sysstat | â Hardware handling |
systemd | â System tools |
sysvinit | â System tools |
szip | â Libraries â Compression and decompression |
taglib | â Libraries â Audio/Sound |
tar | â Development tools |
targetcli-fb | â Hardware handling |
tcl | â Interpreter languages and scripting |
tclap | â Libraries â Text and terminal handling |
tcllib | â Interpreter languages and scripting â tcl libraries/modules |
tcpdump | â Networking applications |
tcping | â Networking applications |
tcpreplay | â Networking applications |
tftpd | â Networking applications |
thrift | â Libraries â Networking |
thttpd | â Networking applications |
ti-gfx | â Hardware handling |
ti-uim | â Hardware handling |
ti-utils | â Hardware handling |
tidsp-binaries | â Audio and video applications |
tiff | â Libraries â Graphics |
time | â Shell and utilities |
tinc | â Networking applications |
tinyalsa | â Libraries â Audio/Sound |
tinyhttpd | â Networking applications |
tinymembench | â Debugging, profiling and benchmark |
tinyxml | â Libraries â JSON/XML |
tinyxml2 | â Libraries â JSON/XML |
tmux | â Shell and utilities |
tn5250 | â Networking applications |
tor | â Networking applications |
torsmo | â Graphic libraries and applications (graphic/text) |
tovid | â Audio and video applications |
trace-cmd | â Debugging, profiling and benchmark |
transmission | â Networking applications |
tree | â Development tools |
tremor (fixed point vorbis decoder) | â Libraries â Audio/Sound |
triggerhappy | â Hardware handling |
trinity | â Debugging, profiling and benchmark |
tslib | â Libraries â Hardware handling |
tstools | â Audio and video applications |
tvheadend | â Networking applications |
twm | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
twolame | â Audio and video applications |
u-boot tools | â Hardware handling |
udisks | â Hardware handling |
udpcast | â Networking applications |
uemacs | â Text editors and viewers |
ulogd | â Networking applications |
unionfs (FUSE) | â Filesystem and flash utilities |
unixodbc | â Libraries â Database |
upmpdcli | â Audio and video applications |
urg | â Libraries â Hardware handling |
usb_modeswitch | â Hardware handling |
usb_modeswitch_data | â Hardware handling |
usbmount | â Hardware handling |
usbredir | â Libraries â Networking |
usbutils | â Hardware handling |
ushare | â Networking applications |
ussp-push | â Networking applications |
ustr | â Libraries â Text and terminal handling |
util-linux | â System tools |
util-macros | â Graphic libraries and applications (graphic/text) â X11R7 Utilities |
ux500-firmware | â Hardware handling â Firmware |
valgrind | â Debugging, profiling and benchmark |
vde2 | â Networking applications |
videoproto | â Graphic libraries and applications (graphic/text) â X11R7 X protocols |
viewres | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
vim | â Text editors and viewers |
vlc | â Audio and video applications |
vnstat | â Networking applications |
vo-aacenc | â Libraries â Audio/Sound |
vorbis-tools | â Audio and video applications |
vpnc | â Networking applications |
vsftpd | â Networking applications |
vtun | â Networking applications |
w_scan | â Hardware handling |
wavpack | â Audio and video applications |
wayland | â Libraries â Graphics |
webkit | â Libraries â Graphics |
WebKit Module | â Graphic libraries and applications (graphic/text) |
webp | â Libraries â Graphics |
webrtc-audio-processing | â Libraries â Audio/Sound |
weston | â Graphic libraries and applications (graphic/text) |
wf111 | â Hardware handling |
wget | â Networking applications |
whetstone | â Debugging, profiling and benchmark |
which | â Shell and utilities |
whois | â Networking applications |
windowswmproto | â Graphic libraries and applications (graphic/text) â X11R7 X protocols |
wine | â Miscellaneous |
wipe | â Hardware handling |
wireless tools | â Networking applications |
wireless-regdb | â Networking applications |
wireshark | â Networking applications |
wmctrl | â Graphic libraries and applications (graphic/text) |
wpa_supplicant | â Networking applications |
wsapi | â Interpreter languages and scripting â Lua libraries/modules |
wvdial | â Networking applications |
wvstreams | â Libraries â Networking |
x11perf | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
x11vnc | â Graphic libraries and applications (graphic/text) |
x264 | â Libraries â Multimedia |
xauth | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xavante | â Interpreter languages and scripting â Lua libraries/modules |
xbacklight | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xbiff | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xbitmaps | â Graphic libraries and applications (graphic/text) â X11R7 Other data |
xcalc | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xcb-proto | â Graphic libraries and applications (graphic/text) â X11R7 X protocols |
xcb-util | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
xcb-util-cursor | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
xcb-util-image | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
xcb-util-keysyms | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
xcb-util-renderutil | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
xcb-util-wm | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
xclipboard | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xclock | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xcmiscproto | â Graphic libraries and applications (graphic/text) â X11R7 X protocols |
xcmsdb | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xcompmgr | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xconsole | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xcursor-transparent-theme | â Graphic libraries and applications (graphic/text) â X11R7 Other data |
xcursorgen | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xdata_xcursor-themes | â Graphic libraries and applications (graphic/text) â X11R7 Other data |
xdbedizzy | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xditview | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xdm | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xdpyinfo | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xdriinfo | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xedit | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
Xenomai Userspace | â Real-Time |
xerces-c++ | â Libraries â JSON/XML |
xev | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xextproto | â Graphic libraries and applications (graphic/text) â X11R7 X protocols |
xeyes | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xf86-input-evdev | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-input-joystick | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-input-keyboard | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-input-libinput | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-input-mouse | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-input-synaptics | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-input-tslib | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-input-vmmouse | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-input-void (deprecated) | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-video-ark | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-video-ast | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-video-ati | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-video-cirrus | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-video-dummy | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-video-fbdev | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-video-geode | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-video-glide | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-video-glint | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-video-i128 | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-video-imx | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-video-imx-viv | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-video-intel | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-video-mach64 | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-video-mga | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-video-neomagic | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-video-nv | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-video-openchrome | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-video-r128 | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-video-savage | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-video-siliconmotion | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-video-sis | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-video-tdfx | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-video-tga | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-video-trident | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-video-v4l | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-video-vesa | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-video-vmware | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-video-voodoo | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86-video-wsfb | â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
xf86bigfontproto | â Graphic libraries and applications (graphic/text) â X11R7 X protocols |
xf86dga | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xf86dgaproto | â Graphic libraries and applications (graphic/text) â X11R7 X protocols |
xf86driproto | â Graphic libraries and applications (graphic/text) â X11R7 X protocols |
xf86vidmodeproto | â Graphic libraries and applications (graphic/text) â X11R7 X protocols |
xfd | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xfindproxy | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xfontsel | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xfs | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xfsinfo | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xfsprogs | â Filesystem and flash utilities |
xgamma | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xgc | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xhost | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xineramaproto | â Graphic libraries and applications (graphic/text) â X11R7 X protocols |
xinetd | â Networking applications |
xinit | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xinput | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xinput-calibrator | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xkbcomp | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xkbevd | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xkbprint | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xkbutils | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xkeyboard-config | â Graphic libraries and applications (graphic/text) |
xkill | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xl2tp | â Networking applications |
xload | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xlogo | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xlsatoms | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xlsclients | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xlsfonts | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xmag | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xman | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xmessage | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xmh | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
XML Patterns Module | â Graphic libraries and applications (graphic/text) |
xmlstarlet | â Shell and utilities |
xmodmap | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xmore | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xorg-server | â Graphic libraries and applications (graphic/text) â X11R7 Servers |
xorriso | â Hardware handling |
xpr | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xprop | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xproto | â Graphic libraries and applications (graphic/text) â X11R7 X protocols |
xproxymanagementprotocol | â Graphic libraries and applications (graphic/text) â X11R7 X protocols |
xrandr | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xrdb | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xrefresh | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xscreensaver | â Graphic libraries and applications (graphic/text) |
xset | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xsetmode | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xsetpointer | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xsetroot | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xsm | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xstdcmap | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xtables-addons | â Networking applications |
xterm | â Graphic libraries and applications (graphic/text) |
xtrans | â Graphic libraries and applications (graphic/text) â X11R7 Libraries |
xvidtune | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xvinfo | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xvkbd | â Graphic libraries and applications (graphic/text) |
xwd | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xwininfo | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xwud | â Graphic libraries and applications (graphic/text) â X11R7 Applications |
xz-utils | â Compressors and decompressors |
yajl | â Libraries â JSON/XML |
yaml-cpp | â Libraries â JSON/XML |
yasm | â Development tools |
yavta | â Audio and video applications |
ympd | â Audio and video applications |
zd1211-firmware | â Hardware handling â Firmware |
zeromq | â Libraries â Networking |
zlib | â Libraries â Compression and decompression |
zlog | â Libraries â Logging |
zmqpp | â Libraries â Networking |
znc | â Networking applications |
zsh | â Shell and utilities |
zxing | â Libraries â Graphics |
zyre | â Libraries â Networking |
These are the virtual packages known to Buildroot, with the
+corresponding symbols and providers.
| Virtual packages | Symbols | Providers |
|---|---|---|
cryptodev |
| cryptodev-linux, ocf-linux |
jpeg |
| jpeg, jpeg-turbo |
libegl |
| mesa3d (w/ OpenGL EGL), gpu-amd-bin-mx51 (also imx53), gpu-viv-bin-mx6q, nvidia-driver (w/ X.org drivers), nvidia-tegra23 binaries, rpi-userland, sunxi-mali, ti-gfx |
libgl |
| mesa3d (w/ DRI swrast driver), mesa3d (w/ DRI i915 driver), mesa3d (w/ DRI i965 driver), mesa3d (w/ DRI radeon driver), xf86-video-imx-viv, nvidia-driver (w/ X.org drivers) |
libgles |
| mesa3d (w/ OpenGL ES), gpu-amd-bin-mx51 (also imx53), gpu-viv-bin-mx6q, nvidia-driver (w/ X.org drivers), nvidia-tegra23 binaries, rpi-userland, sunxi-mali, ti-gfx |
libopenmax |
| bellagio, nvidia-tegra23 binaries, rpi-userland |
libopenvg |
| gpu-amd-bin-mx51 (also imx53), gpu-viv-bin-mx6q, rpi-userland |
luainterpreter |
| lua, luajit |
powervr |
| ti-gfx |
udev |
| eudev, systemd |
The following packages are all available in the menu Host utilities.
| Packages |
|---|
host checkpolicy |
host cramfs |
host dfu-util |
host dos2unix |
host dosfstools |
host e2fsprogs |
host e2tools |
host genext2fs |
host genimage |
host genpart |
host lpc3250loader |
host mke2img |
host mtd, jffs2 and ubi/ubifs tools |
host mtools |
host omap-u-boot-utils |
host openocd |
host parted |
host patchelf |
host pwgen |
host qemu |
host sam-ba |
host squashfs |
host sunxi-tools |
host u-boot tools |
host util-linux |
host-imx-usb loader |
The following features are marked as deprecated in Buildroot due to
+them being either too old or unmaintained. They will be removed at
+some point, so stop using them.
+Each deprecated symbol in kconfig depends on a symbol
+BR2_DEPRECATED_SINCE_xxxx_xx, which provides an indication of when
+the feature can be removed: features will not be removed within the
+year following deprecation. For example, a symbol depending on
+BR2_DEPRECATED_SINCE_2013_05 can be removed from 2014.05 onwards.
| Features | Location |
|---|---|
SuperH64 | Target options â Target Architecture |
sstrip | Build options â strip command for binaries on target |
Linux 3.0.x kernel headers | Toolchain â Kernel Headers |
Linux 3.11.x kernel headers | Toolchain â Kernel Headers |
Linux 3.13.x kernel headers | Toolchain â Kernel Headers |
Linux 3.15.x kernel headers | Toolchain â Kernel Headers |
Linux 3.16.x kernel headers | Toolchain â Kernel Headers |
Linux 3.17.x kernel headers | Toolchain â Kernel Headers |
gcc 4.5.x | Toolchain â GCC compiler Version |
gdb 7.7.x | Toolchain â GDB debugger Version |
xf86-input-void | Target packages â Graphic libraries and applications (graphic/text) â X11R7 Drivers |
blackbox | Target packages â Graphic libraries and applications (graphic/text) |
libungif | Target packages â Libraries â Graphics |
cups | Target packages â Networking applications |
foomatic_filters | Target packages â Networking applications |
gutenprint | Target packages â Networking applications |
hplip | Target packages â Networking applications |
samba | Target packages â Networking applications |
custom patch dir | Bootloaders |
Custom Network Settings | Bootloaders |