Go to file
Tzu-Jung Lee 396e92ed2e tstools: new package
[Thomas: properly indent help text, add largefile dependency, remove
unneeded libpcap dependency, remove unneeded CLEAN_CMDS, reorder build
and install commands, remove uneeded <pkg>_INSTALL_STAGING,
<pkg>_INSTALL_TARGET and <pkg>_INSTALL_IMAGES variables, move from
package/multimedia/ to package/, add license details, rename patch to
remove version number in the patch filename.]

Signed-off-by: Tzu-Jung Lee <tjlee@ambarella.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2013-07-27 16:09:38 +02:00
arch arch/arm: add support for thumb(1) mode 2013-07-18 00:25:07 +02:00
board
boot u-boot: support custom u-boot.bin name 2013-07-26 21:18:23 +02:00
configs defconfig/rpi: bump kernel for misc fixes 2013-07-19 00:33:28 +02:00
docs system: add option to pass extra args to post-build and post-image scripts 2013-07-10 08:52:21 +02:00
fs fix white spaces 2013-07-20 21:13:57 +02:00
linux linux: bump 3.10.x stable version 2013-07-22 13:09:10 +02:00
package tstools: new package 2013-07-27 16:09:38 +02:00
support fix white spaces 2013-07-20 21:13:57 +02:00
system fix white spaces 2013-07-20 21:13:57 +02:00
toolchain toolchain/buildroot: properly handle SSP 2013-07-27 13:16:50 +02:00
.defconfig
.gitignore
CHANGES
Config.in
Config.in.legacy toolchain: remove the old BR2_VFP_FLOAT option 2013-07-16 15:13:57 +02:00
COPYING
Makefile Makefile: unexport RUBYOPT 2013-07-12 13:31:11 +02:00
Makefile.legacy

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