Ei kuvausta

Yann E. MORIN 2ee00d0964 docs: really move the website 9 vuotta sitten
arch 158001f57b Turn the static lib option into a choice with more options 9 vuotta sitten
board b8f45e7a09 boards/raspberrypi: fix rootfs.tar path in readme 9 vuotta sitten
boot 6781302444 boot/uboot: Remove obsolete CONFIG_NOSOFTFLOAT flag 9 vuotta sitten
configs 23da43ae12 configs: add a DT-enabled Raspberry Pi defconfig 9 vuotta sitten
docs 2ee00d0964 docs: really move the website 9 vuotta sitten
fs 5d4734084d package: indentation cleanup 9 vuotta sitten
linux f9ed1936ae linux: bump default to version 3.18.3 9 vuotta sitten
package b90fa707f3 lightning: add -lintl only when needed 9 vuotta sitten
support 8868051262 kconfig/lxdialog: get ncurses CFLAGS with pkg-config 9 vuotta sitten
system 14af550d5e eudev: really bump version 9 vuotta sitten
toolchain 054269ac0e toolchain-external: split target installation from staging installation 9 vuotta sitten
.defconfig b24c3215c1 buildroot: get rid of s390 support 15 vuotta sitten
.gitignore 145508473c update gitignore 11 vuotta sitten
CHANGES 9a5434fbfc Update for 2014.11 9 vuotta sitten
COPYING 1aeaae4990 clarify license and fix website license link 15 vuotta sitten
Config.in f1d3e09895 Build shared libraries only as the default 9 vuotta sitten
Config.in.legacy 0120d9f362 package/strongswan: add tools option deprecation notice 9 vuotta sitten
Makefile 0515fe4566 Makefile: pass host PKG_CONFIG_PATH at "make menuconfig" time 9 vuotta sitten
Makefile.legacy af97c94b70 Makefile.legacy: fix recursive invocation with BUILDROOT_DL_DIR and _CONFIG 10 vuotta sitten
README f0d1fbe6f3 docs: Move README file to root 10 vuotta sitten

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= 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