Buildroot is a simple, efficient and easy-to-use tool to generate embedded
Linux systems through cross-compilation.

The documentation can be found in docs/manual. You can generate a text
document with 'make manual-text' and read output/docs/manual/manual.text.
Online documentation can be found at http://buildroot.org/docs.html
https://buildroot.org/

Maxime Hadjinlian f0d1fbe6f3 docs: Move README file to root 12 лет назад
arch e543f5a104 arch: remove sh2, sh3 and sh3eb support 12 лет назад
board 4d6e8111e4 configs: add SoCkit defconfig 12 лет назад
boot 7961d45c24 gummiboot: new package 12 лет назад
configs 3e78a7daa9 configs/raspberrypi: bump kernel version 12 лет назад
docs f0d1fbe6f3 docs: Move README file to root 12 лет назад
fs a24877586a Makefile: add support for top-level parallel make 12 лет назад
linux b108fdcb83 Merge branch 'next' 12 лет назад
package 878c04b8cc samba4: fix readline support 12 лет назад
support a5a309642a toolchain/external: check kernel headers version for custom toolchain 12 лет назад
system b108fdcb83 Merge branch 'next' 12 лет назад
toolchain 71516ab9e8 glibc: needs MMU 12 лет назад
.defconfig b24c3215c1 buildroot: get rid of s390 support 17 лет назад
.gitignore 145508473c update gitignore 12 лет назад
CHANGES a6cfaea44e Update for 2014.02 12 лет назад
COPYING 1aeaae4990 clarify license and fix website license link 16 лет назад
Config.in b108fdcb83 Merge branch 'next' 12 лет назад
Config.in.legacy 5562be136c xlib_libpthread-stubs: Rename package to libpthread-stubs 12 лет назад
Makefile fbb3b86202 Makefile: ensure system is built even if no filesystem image is selected 12 лет назад
Makefile.legacy af97c94b70 Makefile.legacy: fix recursive invocation with BUILDROOT_DL_DIR and _CONFIG 12 лет назад
README f0d1fbe6f3 docs: Move README file to root 12 лет назад

README

To build and use the buildroot stuff, do the following:

1) run 'make menuconfig'
2) select the packages you wish to compile
3) run 'make'
4) wait while it compiles
5) Use your shiny new root filesystem. Depending on which sort of
root filesystem you selected, you may want to loop mount it,
chroot into it, nfs mount it on your target device, burn it
to flash, or whatever is appropriate for your target system.

You do not need to be root to build or run buildroot. Have fun!

Offline build:
==============

In order to do an offline-build (not connected to the net), fetch all
selected source by issuing a
$ make source

before you disconnect.
If your build-host is never connected, then you have to copy buildroot
and your toplevel .config to a machine that has an internet-connection
and issue "make source" there, then copy the content of your dl/ dir to
the build-host.

Building out-of-tree:
=====================

Buildroot supports building out of tree with a syntax similar
to the Linux kernel. To use it, add O= to the
make command line, E.G.:

$ make O=/tmp/build

And all the output files (including .config) will be located under /tmp/build.

More finegrained configuration:
===============================

You can specify a config-file for uClibc:
$ make UCLIBC_CONFIG_FILE=/my/uClibc.config

And you can specify a config-file for busybox:
$ make BUSYBOX_CONFIG_FILE=/my/busybox.config

To use a non-standard host-compiler (if you do not have 'gcc'),
make sure that the compiler is in your PATH and that the library paths are
setup properly, if your compiler is built dynamically:
$ make HOSTCC=gcc-4.3.orig HOSTCXX=gcc-4.3-mine

Depending on your configuration, there are some targets you can use to
use menuconfig of certain packages. This includes:
$ make HOSTCC=gcc-4.3 linux-menuconfig
$ make HOSTCC=gcc-4.3 uclibc-menuconfig
$ make HOSTCC=gcc-4.3 busybox-menuconfig

Please feed suggestions, bug reports, insults, and bribes back to the
buildroot mailing list: buildroot@buildroot.org