Go to file
2007-01-11 07:27:37 +00:00
docs - add some more useful hints 2006-12-22 12:11:06 +00:00
package add tiff package 2007-01-11 07:27:37 +00:00
target - BR2_TARGET_ROOTFS_EXT2_RESBLKS is ignored if it is 0. It should be used if it is 0 (since 0 means something here--"do not reserve any blocks". 2006-12-22 12:34:35 +00:00
toolchain - Adjust patches to take recent upstream fixes into account. 2007-01-08 18:35:27 +00:00
.defconfig
Config.in
defconfig rework the default x86 target 2006-12-13 11:53:00 +00:00
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.