Go to file
Maxime Ripard 22fde22e35 Create and mount /dev/shm
The /dev/shm directory is neither created nor mounted as tmpfs as boot
time. This will cause troubles when using named semaphores on the
system.

Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-07-03 21:20:49 +02:00
board qemu/mipsel-malta: switch to kernel 2.6.38.5 2011-05-03 20:45:23 +02:00
boot barebox: bump version 2011-05-15 00:07:28 +02:00
configs sheevaplug_defconfig: bump kernel version 2011-06-24 11:34:48 +02:00
docs Update for 2011.05 2011-05-27 16:18:21 +02:00
fs Create and mount /dev/shm 2011-07-03 21:20:49 +02:00
linux linux: bump 2.6.39.x stable version 2011-06-24 11:34:24 +02:00
package sqlite: update to version 3.7.6.3 2011-07-03 21:13:58 +02:00
scripts setlocalversion: fix svn revision l10n-ism 2011-05-25 23:27:22 +02:00
target Move rootfs content options under system configuration 2011-05-12 23:40:05 +02:00
toolchain toolchain/gcc: bump 4.6.x version to 4.6.1 2011-06-28 15:19:13 +02: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-06-26 23:07:01 +02:00
Config.in Config.in: use kent.dl.sourceforge.net by default 2011-02-09 23:09:48 +01:00
COPYING clarify license and fix website license link 2009-05-08 09:29:41 +02:00
Makefile Remove unused variable definitions 2011-06-12 21:56:09 +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 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