52 lines
1.7 KiB
Plaintext
52 lines
1.7 KiB
Plaintext
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
|
|
|
|
And you can specify a config-file for busybox:
|
|
$ make BUSYBOX_CONFIG_FILE=/my/busybox.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.
|