Go to file
2007-01-16 01:29:38 +00:00
docs - add some more useful hints 2006-12-22 12:11:06 +00:00
package Remove all of the binaries except for the one used for the target even though it is a MIPS binary and cannot be used. This package is still crap. 2007-01-16 01:29:38 +00:00
target - andersee, why was this duplicated and hardcoded here? 2007-01-15 17:34:58 +00:00
toolchain - bump version to 2.6.19.2 2007-01-15 15:55:43 +00:00
.defconfig
Config.in
defconfig
Makefile link $(STAGING_DIR)/usr/lib to $(STAGING_DIR)/lib 2007-01-10 06:55:27 +00:00

To build and use the buildroot stuff, do the following:

1) run 'make'
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

More finegrained configuration:
===============================

You can specify a config-file for uClibc:
$ make UCLIBC_CONFIG_FILE=/my/uClibc.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.