Go to file
Peter Korsgaard 95313e2000 neon: fix compilation without xml support
webdav needs xml support, so disable it if no xml support is selected,
otherwise configure could get confused about a host xml2-config script.
2008-08-26 20:47:12 +00:00
docs Kconfig: remove 'default n' 2008-07-17 20:01:44 +00:00
package neon: fix compilation without xml support 2008-08-26 20:47:12 +00:00
project buildroot: add /etc/br-version with version info to target dir 2008-03-31 19:50:05 +00:00
scripts Kconfig: remove 'default n' 2008-07-17 20:01:44 +00:00
target Update AT91 patches to latest Linux 2008-08-23 20:45:42 +00:00
toolchain toolchain/gdb: unbreak target gdb support 2008-08-24 07:48:22 +00:00
.defconfig defconfig: remove settings with default values 2008-04-04 07:12:42 +00:00
Config.in buildroot: remove trailing spaces 2008-08-04 19:07:05 +00:00
Makefile buildroot: remove trailing spaces 2008-08-04 19:07:05 +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.

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