Go to file
Gustavo Zacarias 9245aef2b5 configs/p1010rdb: bump to kernel 3.17.4
Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2014-11-27 20:20:55 +01:00
arch
board configs/p1010rdb: bump to kernel 3.17.4 2014-11-27 20:20:55 +01:00
boot boot/grub: use install instead of cp 2014-11-22 19:01:12 +01:00
configs configs/p1010rdb: bump to kernel 3.17.4 2014-11-27 20:20:55 +01:00
docs Update for 2014.11-rc1 2014-11-12 23:11:07 +01:00
fs fs/iso9660: use install instead of cp 2014-11-22 19:01:27 +01:00
linux
package package/tvheadend: Add support for liburiparser 2014-11-26 22:49:23 +01:00
support support/scripts/scancpan: generate hash file 2014-11-22 19:43:00 +01:00
system
toolchain
.defconfig
.gitignore
CHANGES Update for 2014.11-rc1 2014-11-12 23:11:07 +01:00
Config.in
Config.in.legacy
COPYING
Makefile Kickoff 2015.02 cycle 2014-11-14 14:52:59 +01:00
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