Thomas De Schampheleire b47c8cc8aa manual: clarify format of comments about dependency on Linux kernel 12 anni fa
..
images a08538fd5a docs/images: optimize small images to speed up page loading 15 anni fa
manual b47c8cc8aa manual: clarify format of comments about dependency on Linux kernel 12 anni fa
README f55d8dff35 docs: remove outdated files 15 anni fa
about.html 439f48736b docs/about.html: we support internal (e)glibc toolchains as well now 12 anni fa
copyright.txt 26b11df79c Update copyright info for 2013 12 anni fa
developer.html e2cac48876 docs/: announce move to git 16 anni fa
docs.html d40d77ff70 docs: update links to the manual 13 anni fa
download.html 9b3904543c Update for 2013.11 12 anni fa
favicon.ico b90b9cc70a docs: add favicon / robots.txt 14 anni fa
footer.html 26b11df79c Update copyright info for 2013 12 anni fa
git.html eb19e82861 docs/git.html: slightly reword for git 13 anni fa
header.html 4de330fa2d docs: add a page to thank our sponsors 12 anni fa
index.html c772f41f05 docs/: show about.html as index page 17 anni fa
lists.html 0bf480856e repair ML search knob 14 anni fa
news.html b8160c39ce docs/news.html: add 2013.11 announcement link 12 anni fa
robots.txt b90b9cc70a docs: add favicon / robots.txt 14 anni fa
sponsors.html 4de330fa2d docs: add a page to thank our sponsors 12 anni fa
stylesheet.css a454cb61c0 stylesheet.css: cleaned up css code 15 anni fa

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 sort of
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!

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.

Building out-of-tree:
=====================

Buildroot supports building out of tree with a syntax similar
to the Linux kernel. To use it, add O= to the
make command line, E.G.:

$ make O=/tmp/build

And all the output files (including .config) will be located under /tmp/build.

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 linux-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 the
buildroot mailing list: buildroot@uclibc.org