Go to file
2009-02-13 08:34:01 +00:00
docs docs/news.html: announce 2009.02 2009-02-12 09:33:01 +00:00
package mpfr: bump version 2009-02-13 08:34:01 +00:00
project BR2_BANNER: set to 'Welcome to Buildroot' 2009-01-15 14:50:03 +00:00
scripts setlocalversion: sync with HEAD of kernel git 2009-02-03 16:24:13 +00:00
target u-boot: don't touch config.h unless explicitly requested by user 2009-02-10 15:19:57 +00:00
toolchain kernel-headers: bump 2.6.27/2.6.28 stable versions 2009-02-12 20:21:12 +00:00
.defconfig buildroot: get rid of s390 support 2009-01-12 14:36:14 +00:00
Config.in buildroot: update version for 2009.05 development 2009-02-12 09:02:36 +00:00
Makefile make update shoudl save to PROJECT_defconfig 2009-01-31 20:38:55 +00:00
TODO - mark the autotools.in part as taken 2007-09-28 20:52:09 +00: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 sortof
    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!

 -Erik

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 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 linux26-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