Go to file
Peter Korsgaard 4ce8af8632 Remove references to module-init-tools
Now that it is replaced by kmod.

Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-09-02 23:01:34 +02:00
arch nios2: Add new architecture 2013-09-02 21:38:45 +02:00
board Merge branch 'next' 2013-08-31 23:32:29 +02:00
boot barebox: bump to version 2013.08.0 2013-08-07 18:51:42 +02:00
configs Merge branch 'next' 2013-08-31 23:32:29 +02:00
docs Remove references to module-init-tools 2013-09-02 23:01:34 +02:00
fs fix white spaces 2013-07-20 21:13:57 +02:00
linux linux: use kmod instead of module-init-tools 2013-09-02 22:59:27 +02:00
package Remove references to module-init-tools 2013-09-02 23:01:34 +02:00
support Merge branch 'next' 2013-08-31 23:32:29 +02:00
system host-mkpasswd: new package 2013-08-10 19:49:32 +02:00
toolchain toolchain-external: Add Sourcery CodeBench for Nios-II 2013-09-02 21:39:35 +02: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 2013.08 2013-08-31 00:33:13 +02:00
Config.in config: reorder top-level menu 2013-08-28 16:21:34 +02:00
Config.in.legacy module-init-tools: remove package 2013-09-02 22:59:27 +02:00
COPYING clarify license and fix website license link 2009-05-08 09:29:41 +02:00
Makefile Merge branch 'next' 2013-08-31 23:32:29 +02:00
Makefile.legacy legacy: add error target for host-pkg-config 2012-11-30 12:07:09 -08: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