kumquat-buildroot/docs
2008-03-13 17:16:30 +00:00
..
images - update valid HTML pic and temporarily enable referer checking 2007-01-19 11:12:46 +00:00
about.html
buildroot.html - trivial style fixes. 2007-09-19 09:08:10 +00:00
copyright.txt
developer.html Update Instructions for applying for Buildroot write access 2007-07-12 14:46:03 +00:00
docs.html
download.html
footer.html
Glibc_vs_uClibc.html HTMLized glibc vs uclibc and added to docs 2008-03-07 13:34:02 +00:00
header.html - remove validator 2007-01-19 19:21:03 +00:00
index.html
lists.html - make sure that URLs are standard conforming 2007-01-19 09:24:39 +00:00
news.html
patches.html add some documentation about buildroot's patch system 2008-03-13 17:16:30 +00:00
README - document BUSYBOX_CONFIG_FILE 2007-09-02 17:44:09 +00:00
README.diskimage - add a sample README.diskimage for i386 2007-09-27 21:32:50 +00:00
stylesheet.css
subversion.html

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.