Go to file
2007-07-17 00:22:39 +00:00
docs Fix Document style 2007-07-12 17:04:05 +00:00
package Build proftpd with IPv6 support only if the toolchain was configured as such. 2007-07-17 00:22:39 +00:00
project BSP Patch: 2007-07-12 13:11:03 +00:00
target A number of fixes including placing of the final image into the 'binaries' directory. Moved INITRAMFS_TARGET to the correct location as modules from the built kernel were not being installed until after the INITRAMFS had been built. Fixed config options for INITRAMFS to be correct and cleaned up whitespace/tab issues. 2007-07-17 00:20:32 +00:00
toolchain Allow selection of RPC and IPv6 options for an external toolchain. 2007-07-17 00:18:54 +00:00
.defconfig - update defconfig 2007-06-07 12:54:29 +00:00
Config.in BSP Patch: 2007-07-12 13:11:03 +00:00
Makefile Define HOSTLN to allow gzip to build for non-x86 target 2007-07-15 21:54:11 +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

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

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.