Go to file
Thomas De Schampheleire f6fc9abd10 pkg-virtual: simplify definition of FOO_VERSION to 'virtual'
As mentioned in the e-mail accompanying the introduction of the pkg-virtual
infrastructure [1], the definition of FOO_VERSION is 'strange'.

After the cleanup of single/double dollar signs in inner-generic-package,
the special construction in pkg-virtual is no longer needed and can be
simplified.

Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>

[1] http://lists.busybox.net/pipermail/buildroot/2014-April/093670.html
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2014-06-14 19:10:08 +02:00
arch
board
boot
configs
docs infra: consistently use double dollar signs inside inner-xxx-targets 2014-06-14 19:09:54 +02:00
fs infra: consistently use double dollar signs inside inner-xxx-targets 2014-06-14 19:09:54 +02:00
linux
package pkg-virtual: simplify definition of FOO_VERSION to 'virtual' 2014-06-14 19:10:08 +02:00
support
system systemd: needs kernel headers >= 3.10 2014-06-13 22:32:37 +02:00
toolchain toolchain-external: add CodeSourcery PowerPC 2012.03 2014-06-14 19:04:50 +02:00
.defconfig
.gitignore
CHANGES Update for 2014.05 2014-05-31 09:52:49 +02:00
Config.in kernel headers: remove deprecated version 3.8 2014-06-13 22:27:39 +02:00
Config.in.legacy kernel headers: remove deprecated version 3.8 2014-06-13 22:27:39 +02:00
COPYING
Makefile
Makefile.legacy
README

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@buildroot.org