John Voltz a37d1b117e add some documentation about buildroot's patch system 18 éve
..
images cef68d9464 - update valid HTML pic and temporarily enable referer checking 19 éve
Glibc_vs_uClibc.html dc56871dde HTMLized glibc vs uclibc and added to docs 18 éve
README 673ee97c2f - document BUSYBOX_CONFIG_FILE 18 éve
README.diskimage 39afe93407 - add a sample README.diskimage for i386 18 éve
about.html a9d6aed933 Add a website 21 éve
buildroot.html 53cc639eef - trivial style fixes. 18 éve
copyright.txt a9d6aed933 Add a website 21 éve
developer.html be089760c6 Update Instructions for applying for Buildroot write access 18 éve
docs.html ab213930a2 - point to the buildroot ML instead of the uclibc one. 19 éve
download.html e9b3eb8f73 remove reference to "releases" 20 éve
footer.html a9d6aed933 Add a website 21 éve
header.html 2e37ca7041 - remove validator 19 éve
index.html a9d6aed933 Add a website 21 éve
lists.html 5fada5248a - make sure that URLs are standard conforming 19 éve
news.html a0426f185d Sigh. 19 éve
patches.html a37d1b117e add some documentation about buildroot's patch system 18 éve
stylesheet.css fdb390e971 move docs to subdir 21 éve
subversion.html ab213930a2 - point to the buildroot ML instead of the uclibc one. 19 éve

README

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
or the buildroot mailing list.