Go to file
Thomas Petazzoni d00bd2a1f7 external-toolchain: add Sourcery CodeBench x86/x86_64 2011.09
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2012-03-01 20:26:38 +01:00
board qemu/ppc-g3beige: update readme and use kernel 3.2.6 2012-02-26 23:03:57 +01:00
boot barebox: add 2012.02, remove 2011.11 2012-02-06 23:25:10 +01:00
configs qemu/ppc-g3beige: update readme and use kernel 3.2.6 2012-02-26 23:03:57 +01:00
docs Update copyright year 2012-03-01 14:04:54 +01:00
fs Introduce /run directory 2012-02-02 23:03:13 +01:00
linux linux: bump 3.2.x stable version 2012-02-14 00:26:35 +01:00
package Merge branch 'next' 2012-03-01 14:05:41 +01:00
support pkg-stats: update list of packages to be skipped 2012-02-26 19:46:58 +01:00
target Add the Atom processor in the list of supported x86/x86_64 processors 2012-03-01 20:26:36 +01:00
toolchain external-toolchain: add Sourcery CodeBench x86/x86_64 2011.09 2012-03-01 20:26:38 +01:00
.defconfig buildroot: get rid of s390 support 2009-01-12 14:36:14 +00:00
.gitignore .gitignore: ignore more patch related files 2010-11-18 12:07:23 +01:00
CHANGES kickoff 2012.05 development cycle 2012-03-01 14:03:39 +01:00
Config.in Add basic config infrastructure for host utilities 2012-02-02 20:54:19 +01:00
COPYING clarify license and fix website license link 2009-05-08 09:29:41 +02:00
Makefile Merge branch 'next' 2012-03-01 14:05:41 +01: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 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