Go to file
Ulf Samuelsson 18199aa7b6 Move lzma patches to toolchain/kernel-headers/lzma
They will be applied ONLY if BR2_KERNEL_HEADERS_LZMA is set.

BR2_KERNEL_HEADERS_LZMA defaults to NO, so the user
has to actively set this config flag if lzma is needed.

This means that the default behaviour of buildroot will work
for most users.

Comment from author:

[Brad House]
I find myself having to remove the lzma patches because my build system
doesn't natively have lzma.  I tried to compensate for this by
installing the latest lzma from gentoo's package tree, and apparently,
it accepts different flags than the one these patches expect, so my
kernel build still fails.  Finally, I used the lzma from this buildroot
and compiled it by hand, and it _mostly_ worked.  Regardless, it seems
silly to make this a requirement.  Personally, I gzip my initramfs,
and that's enough compression for me...
2007-08-16 06:26:25 +00:00
docs Cleanup of docs 2007-08-12 23:26:28 +00:00
package Allow user to configure PROGRAM_INVOCATION_NAME 2007-08-15 22:35:26 +00:00
project Move project related info from main Makefile to project dir 2007-08-14 07:45:01 +00:00
target Add programmable start adr/size to at91bootstrap + support for at91sam9260pf 2007-08-15 09:42:33 +00:00
toolchain Move lzma patches to toolchain/kernel-headers/lzma 2007-08-16 06:26:25 +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 Avoid copying TARGET_SKELETON on every 'make' 2007-08-16 05:44:55 +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.