Go to file
Thomas Petazzoni 12d1aa4b69 Remove BR2_HAVE_DEVFILES
This finally removes the BR2_HAVE_DEVFILES option, that was used to
install/keep development files on target. With the recent migration of
the internal backend to the package infrastructure, we had anyway lost
the ability to build gcc for the target, and install the uClibc
development files on the target.

[Peter: also remove support/scripts/copy.sh]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-07-04 09:06:33 +02:00
arch arm: update processor types 2013-06-16 21:12:36 +02:00
board Add support for the Calao-systems TNY-A9G20-LPW 2013-06-02 22:22:04 +02:00
boot uboot: Add ELF target 2013-06-15 23:24:09 +02:00
configs configs: bump kernel in rpi_defconfig for misc fixes 2013-06-27 15:51:02 +02:00
docs uclibc: convert to the package infrastructure 2013-07-04 00:13:23 +02:00
fs Normalize separator size to 80 in remaining makefiles 2013-06-20 17:32:07 +02:00
linux linux: bump 3.9.x stable version 2013-06-28 11:35:07 +02:00
package Remove BR2_HAVE_DEVFILES 2013-07-04 09:06:33 +02:00
support Remove BR2_HAVE_DEVFILES 2013-07-04 09:06:33 +02:00
system system/permissions: make /root group+others non-writable 2013-06-23 21:51:57 +02:00
toolchain Use more sensible names for the external/ctng targets 2013-07-04 00:14:10 +02:00
.defconfig buildroot: get rid of s390 support 2009-01-12 14:36:14 +00:00
.gitignore update gitignore 2013-05-04 12:41:55 +02:00
CHANGES Update for 2013.05 2013-05-31 22:29:04 +02:00
Config.in Remove BR2_HAVE_DEVFILES 2013-07-04 09:06:33 +02:00
Config.in.legacy elf2flt: convert to the package infrastructure 2013-07-03 22:09:12 +02:00
COPYING clarify license and fix website license link 2009-05-08 09:29:41 +02:00
Makefile Remove BR2_HAVE_DEVFILES 2013-07-04 09:06:33 +02:00
Makefile.legacy legacy: add error target for host-pkg-config 2012-11-30 12:07:09 -08: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