kumquat-buildroot/docs
Peter Korsgaard b90b9cc70a docs: add favicon / robots.txt
In the past, these files of the buildroot website weren't under git
version control, but rather were static files added to the git checkout
used by the webserver.

This is no longer the case, so add them to git - And at the same time
use the Buildroot logo for the favicon, rather than reusing the busybox
one.

Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-04-04 22:21:47 +02:00
..
images
about.html
buildroot.html
copyright.txt
developer.html
docs.html
download.html
favicon.ico docs: add favicon / robots.txt 2011-04-04 22:21:47 +02:00
footer.html
git.html
Glibc_vs_uClibc.html
header.html website: add google analytics for statistics 2011-03-01 23:20:16 +01:00
index.html
lists.html
news.html news.html: add 2011.02 announcement link 2011-02-28 22:37:41 +01:00
README
robots.txt docs: add favicon / robots.txt 2011-04-04 22:21:47 +02:00
stylesheet.css

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=<directory> 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