Go to file
Gustavo Zacarias 54942318f9 pciutils: SHARED make opt goes for install too
If we don't pass SHARED when installing we miss the shared library
symlinks (libpci.so & libpci.so.3).

On internal and external toolchains that have a proper cross ldconfig this
isn't a problem as they get created during ldconfig, but it breaks on
toolchains that lack a cross ldconfig to automagically make the symlinks.

Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-01-10 14:52:02 +01:00
board board: Add a Qemu mipsel Malta board 2010-12-17 16:54:51 +01:00
boot barebox: bump version 2011-01-06 12:25:33 +01:00
configs toolchain: drop BR2_CROSS_TOOLCHAIN_TARGET_UTILS option 2010-12-29 23:14:48 +01:00
docs documentation: Update to explain how board support works 2010-12-16 14:35:21 +01:00
fs genext2fs.sh: improve number of blocks calculation 2010-12-30 23:10:21 +01:00
linux linux: add 2.6.37, remove 2.6.36 2011-01-06 08:44:11 +01:00
package pciutils: SHARED make opt goes for install too 2011-01-10 14:52:02 +01:00
scripts scripts: get rid of outdated buildall script 2010-10-04 11:44:08 +02:00
target toolchain: drop BR2_CROSS_TOOLCHAIN_TARGET_UTILS option 2010-12-29 23:14:48 +01:00
toolchain kernel-headers: remove deprecated 2.6.30/2.6.31 versions 2011-01-10 12:29:58 +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 CHANGES: update with recent changes 2011-01-03 00:11:40 +01:00
Config.in toolchain: move sysroot to host dir 2010-12-28 22:38:47 +01:00
COPYING clarify license and fix website license link 2009-05-08 09:29:41 +02:00
Makefile toolchain: do staging symlink 2011-01-02 22:55:36 +01:00
TODO coreutils: add TODO note about stripping the installed binaries 2009-07-31 15:00:15 +02: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 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