Nessuna descrizione

Yann E. MORIN 7a0c134e7c boards/raspberrypi: update instructions for Raspberry Pi 2 9 anni fa
arch 80be8753d5 arch/avr32: decommission for real 9 anni fa
board 7a0c134e7c boards/raspberrypi: update instructions for Raspberry Pi 2 9 anni fa
boot 357a2c2715 barebox: migrate to the kconfig infrastructure 9 anni fa
configs 7f6a9f6e89 configs: add Raspberry Pi 2 defconfig 9 anni fa
docs 2165267699 Update for 2015.02-rc1 9 anni fa
fs 66ee6dc872 fs/tar: only store numeric uid/gid 9 anni fa
linux 67596b6b6e linux: get rid of avr32 specifics 9 anni fa
package 9085505c02 git: bump version to 2.3.1 9 anni fa
support 8868051262 kconfig/lxdialog: get ncurses CFLAGS with pkg-config 9 anni fa
system 0fa62b4ca5 system: Defaulting TZ_LOCALTIME to UTC 9 anni fa
toolchain ee2ccf0d64 toolchain: Enable the internal toolchain for nios2 9 anni fa
.defconfig a46007daa7 arch: kill avr32 9 anni fa
.gitignore 145508473c update gitignore 11 anni fa
CHANGES 2165267699 Update for 2015.02-rc1 9 anni fa
COPYING 1aeaae4990 clarify license and fix website license link 15 anni fa
Config.in f1d3e09895 Build shared libraries only as the default 9 anni fa
Config.in.legacy 8d702aca30 legacy: add missing option for util-linux' wdctl 9 anni fa
Makefile 2165267699 Update for 2015.02-rc1 9 anni fa
Makefile.legacy af97c94b70 Makefile.legacy: fix recursive invocation with BUILDROOT_DL_DIR and _CONFIG 10 anni fa
README f0d1fbe6f3 docs: Move README file to root 10 anni fa

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