Go to file
Bernhard Reutner-Fischer ea8b1fa6a6 - put LZMA into generic flags
- some additional cleanups while at it
2007-09-22 17:30:38 +00:00
docs - trivial style fixes. 2007-09-19 09:08:10 +00:00
package - fix typo in .config filename 2007-09-22 17:29:23 +00:00
project - Subsume and collaps toolchain options in one menu 2007-09-22 14:16:25 +00:00
target - put LZMA into generic flags 2007-09-22 17:30:38 +00:00
toolchain - bump version (forgot this hunk for r19941) 2007-09-22 16:42:25 +00:00
.defconfig - update defconfig 2007-06-07 12:54:29 +00:00
Config.in - Subsume and collaps toolchain options in one menu 2007-09-22 14:16:25 +00:00
Makefile - set and export VERBOSE if V= was requested 2007-09-22 14:19:22 +00:00
TODO - add a TODO file to record misc possible extensions/improvements 2007-07-31 18:25:29 +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.

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-standart 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:
	Erik Andersen <andersen@codepoet.org>
or the buildroot mailing list.