Go to file
Peter Korsgaard 8a46d4bf1f {rand,allyes}packageconfig: ensure legacy test options don't get enabled
The legacy BR2_PACKAGE_* options in Config.in.legacy are not supposed to
be user selectable, so {rand,allyes}packageconfig shouldn't enable them.

Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-12-01 18:13:05 -08:00
arch xtensa: use uppercase for configurations and modified overlay structure 2012-11-21 11:08:50 +01:00
board qemu/mips64-malta: update to use kernel 3.6.6 2012-11-15 22:49:45 +01:00
boot Remove unused barebox 2012.07 string 2012-11-21 11:17:12 +01:00
configs qemu/mips64-malta: update to use kernel 3.6.6 2012-11-15 22:49:45 +01:00
docs Update for 2012.11-rc2 2012-11-30 22:59:02 -08:00
fs cramfs.mk: drop invalid -q option 2012-11-29 23:25:09 -08:00
linux linux: bump 3.6.x stable version 2012-11-28 13:59:04 -08:00
package libsigc: Don't copy devel documentation onto target 2012-11-30 22:08:03 -08:00
support Warn the user about the usage of output/target as the root filesystem 2012-11-17 17:12:49 +01:00
system Add /var/www to device table 2012-11-30 11:48:52 -08:00
toolchain toolchain-external: fix installation of libthread_db 2012-11-30 13:57:49 -08: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 Update for 2012.11-rc2 2012-11-30 22:59:02 -08:00
Config.in pkg-infra: introduce errors for legacy API 2012-11-30 12:06:40 -08:00
Config.in.legacy legacy: BR2_PACKAGE_LIBINTL is replaced by gettext 2012-11-30 12:07:35 -08:00
COPYING clarify license and fix website license link 2009-05-08 09:29:41 +02:00
Makefile {rand,allyes}packageconfig: ensure legacy test options don't get enabled 2012-12-01 18:13:05 -08: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