kumquat-buildroot

NetCube-Systems-Austria/kumquat-buildroot

Go to file

Bernhard Reutner-Fischer 28a36b609a - thinking loud about auto-generating dependencies for make(1) Don't use this, it doesn't work yet. Thoughs welcome. Like: We should probably use the sym->text and not fiddle with the name since the name looses information ('_' != '-' in host-fakeroot). This would not be too robust, i fear, since the name can contain additional, arbitrary info. Also, the real 'depends' are a little bit ugly in kconfig. There doesn't seem to be a nice property that holds reverse deps that are only contain selected symbols. Thoughts?		2007-09-23 20:28:53 +00:00
docs	- trivial style fixes.	2007-09-19 09:08:10 +00:00
package	- thinking loud about auto-generating dependencies for make(1)	2007-09-23 20:28:53 +00:00
project	Ensure project U-Boot dir exists before using it	2007-09-23 10:16:58 +00:00
target	Update atstk1002 config	2007-09-23 10:56:16 +00:00
toolchain	- rename the gcc base_target to the more appropriate term cross_compiler	2007-09-22 21:38:15 +00:00
.defconfig
Config.in
Makefile	Ensure make %_defconfig works without error - now silently	2007-09-23 14:36:04 +00:00
TODO	- add a TODO file to record misc possible extensions/improvements	2007-07-31 18:25:29 +00:00

docs/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 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.