Skip to content
Buildroot, making embedded Linux easy.
Branch: master
Clone or download
Pull request Compare This branch is 30004 commits behind buildroot:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
arch avr32: pass target arch to gcc Nov 6, 2013
board configs: rename rpi_defconfig for consistency Nov 10, 2013
boot
configs
docs
fs
linux
package qt5base: fix posix_fallocate patch Nov 12, 2013
support Makefile: fix out-of-tree builds with multiple targets with 'all' Nov 6, 2013
system
toolchain
.defconfig
.gitignore update gitignore May 4, 2013
CHANGES Update for 2013.11-rc1 Nov 12, 2013
COPYING clarify license and fix website license link May 8, 2009
Config.in Config.in files: whitespace cleanup Nov 11, 2013
Config.in.legacy Config.in.legacy: select BR2_LEGACY for module-init-tools legacy option Nov 10, 2013
Makefile
Makefile.legacy

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=<directory> 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@uclibc.org
You can’t perform that action at this time.