No Description

Will Wagner 6b1ca27b1a yaffs2: new filesystem type 11 years ago
arch 574fa145d8 Disable o32 ABI for MIPS64 architectures 10 years ago
board aac1fed7b9 board/arm/foundation-v8: update defconfig and instructions 10 years ago
boot 1f9a0b3815 grub2: add a configuration option to embed a config file 10 years ago
configs d48eb62608 configs: bump raspberrypi_defconfig to use the latest stable kernel 10 years ago
docs bb068823ab manual: document BR2_GRAPH_DEPTH 10 years ago
fs 6b1ca27b1a yaffs2: new filesystem type 10 years ago
linux 88f1a66441 linux: bump to version 3.14.1 10 years ago
package f27831ae13 yaffs2utils: new package 10 years ago
support 38b81eb172 support: properly check bash is available 10 years ago
system 337fbd549c system: allow setting the local timezone for uClibc 10 years ago
toolchain 5f70a007c8 toolchain: add a hidden config option to enable the toolchain package 10 years ago
.defconfig b24c3215c1 buildroot: get rid of s390 support 15 years ago
.gitignore 145508473c update gitignore 11 years ago
CHANGES 574fa145d8 Disable o32 ABI for MIPS64 architectures 10 years ago
COPYING 1aeaae4990 clarify license and fix website license link 15 years ago
Config.in a920fdd007 uboot: mark custom network settings as deprecated 10 years ago
Config.in.legacy d6a37917dd system: make the zoneinfo list a system option 10 years ago
Makefile 1990e79f14 Makefile: target-generatelocales: add toolchain dependency 10 years ago
Makefile.legacy af97c94b70 Makefile.legacy: fix recursive invocation with BUILDROOT_DL_DIR and _CONFIG 10 years ago
README f0d1fbe6f3 docs: Move README file to root 10 years ago

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