Go to file
Ulf Samuelsson afec678745 Move AVR32 kernel patches to target/device/Atmel/arch-avr32
Add linux-2.6.22.1-008-atmel-gpio_mouse-setup-for-atstk1000-board.patch
	Move AT91  kernel patches to target/device/Atmel/arch-arm
	Change name from "target/device/Atmel/Linux" to "target/device/Atmel/linux"
	"kernel-headers" will apply all patches in $(LINUX26_KERNEL_PATCH_DIR)
		if this is available.
	Define LINUX26_KERNEL_PATCH_DIR in target/device/Atmel/Makefile.in
		as above "arch-arm/kernel-patches-..." if an AT91 or
		as above "arch-avr32/kernel-patches-..." if an AVR32 target is selected
	Test build done for arm,avr32 and x86
2007-08-18 08:46:41 +00:00
docs Add further documentation for BSP patch 2007-08-16 21:54:48 +00:00
package Move fakeroot temps from STAGING_DIR to PROJECT_BUILD_DIR 2007-08-16 18:19:42 +00:00
project Move project related info from main Makefile to project dir 2007-08-14 07:45:01 +00:00
target Move AVR32 kernel patches to target/device/Atmel/arch-avr32 2007-08-18 08:46:41 +00:00
toolchain Move AVR32 kernel patches to target/device/Atmel/arch-avr32 2007-08-18 08:46:41 +00:00
.defconfig - update defconfig 2007-06-07 12:54:29 +00:00
Config.in Added powerpc variant selection 2007-08-14 11:59:46 +00:00
Makefile Move fakeroot temps from STAGING_DIR to PROJECT_BUILD_DIR 2007-08-16 18:19:42 +00:00
TODO - add a TODO file to record misc possible extensions/improvements 2007-07-31 18:25:29 +00: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 sortof
    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!

 -Erik

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.

More finegrained configuration:
===============================

You can specify a config-file for uClibc:
$ make UCLIBC_CONFIG_FILE=/my/uClibc.config

To use a non-standart 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 linux26-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:
	Erik Andersen <andersen@codepoet.org>
or the buildroot mailing list.