Go to file
Ivan Sergeev fc07556408 systemd: fix sed line in "sanitize path in units" hook
The expanded SED variable already contains -e, so the extra -e was being
interpreted as the sed command and causing sed to fail.

Signed-off-by: Ivan Sergeev <vsergeev@kumunetworks.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-02-15 08:21:50 +01:00
arch arch: remove sh2, sh3 and sh3eb support 2014-02-05 12:05:58 +01:00
board beaglebone: update to TI 3.12 kernel 2014-02-10 19:40:27 +01:00
boot barebox: bump to version 2014.02.0 2014-02-10 09:59:49 +01:00
configs configs/raspberrypi: remove packages not strictly required 2014-02-10 22:05:59 +01:00
docs manual: update /dev management section. 2014-02-12 22:14:45 +01:00
fs Makefile: add support for top-level parallel make 2014-02-14 21:09:04 +01:00
linux systemd: bump to v207 2014-02-12 22:14:36 +01:00
package systemd: fix sed line in "sanitize path in units" hook 2014-02-15 08:21:50 +01:00
support infra: replace BUILDROOT_CONFIG with BR2_CONFIG 2014-02-09 17:00:13 +01:00
system systemd: bump to v207 2014-02-12 22:14:36 +01:00
toolchain package: add toolchain dependency to every target package 2014-02-14 21:08:35 +01:00
.defconfig buildroot: get rid of s390 support 2009-01-12 14:36:14 +00:00
.gitignore update gitignore 2013-05-04 12:41:55 +02:00
CHANGES Update for 2014.02-rc1 2014-02-11 12:37:42 +01:00
Config.in infra: replace BUILDROOT_DL_DIR with BR2_DL_DIR. 2014-02-09 11:02:42 +01:00
Config.in.legacy systemd: bump to v207 2014-02-12 22:14:36 +01:00
COPYING clarify license and fix website license link 2009-05-08 09:29:41 +02:00
Makefile core: remove .py/.pyc for Python 2014-02-14 21:51:19 +01:00
Makefile.legacy Makefile.legacy: fix recursive invocation with BUILDROOT_DL_DIR and _CONFIG 2014-02-11 08:14:57 +01:00

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