Go to file
Philippe Reynes f66d4b05e1 board: Add Qemu SH4 r2d configuration
[ Thomas:

   * renamed sh4_defconfig to qemu_sh4_r2d_defconfig, for consistency
     with other Qemu platforms supported
   * renamed board/qemu/sh4 to board/qemu/sh4-r2d
   * minor fixes in the readme.txt
   * remove useless statements in the minimal defconfig
   * switch to a fixed kernel version instead of "same as headers"
]

Signed-off-by: Philippe Reynes <tremyfr@yahoo.fr>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-12-17 16:52:42 +01:00
board board: Add Qemu SH4 r2d configuration 2010-12-17 16:52:42 +01:00
boot u-boot: add CROSS_COMPILE/ARCH when building host tools 2010-12-16 15:06:45 +01:00
configs board: Add Qemu SH4 r2d configuration 2010-12-17 16:52:42 +01:00
docs documentation: Update to explain how board support works 2010-12-16 14:35:21 +01:00
fs Add network scripting folders to fs/skeleton 2010-12-16 15:16:31 +01:00
linux linux: support a space-separated list of patches 2010-12-16 22:30:18 +01:00
package l2tp: convert to gentargets and change to xl2tp 2010-12-14 01:35:41 +01:00
scripts scripts: get rid of outdated buildall script 2010-10-04 11:44:08 +02:00
target xtensa: remove unused and useless skeleton patch 2010-12-17 16:51:41 +01:00
toolchain dependencies: add unzip 2010-12-16 14:43:17 +01:00
.defconfig
.gitignore .gitignore: ignore more patch related files 2010-11-18 12:07:23 +01:00
CHANGES CHANGES: #561/#1651/#1735 are resolved 2010-12-14 20:45:59 +01:00
Config.in Re-add target/generic/Config.in options to menuconfig 2010-12-16 12:19:25 +01:00
COPYING
Makefile toolchain: add support for external toolchain profiles and download 2010-12-13 21:56:49 +01:00
TODO

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.

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