Go to file
2007-08-14 07:45:01 +00:00
docs Cleanup of docs 2007-08-12 23:26:28 +00:00
package Add links to 'usr/include/freetype2/freetype' to 'include' and 'usr/include'. Add PHONY targets 2007-08-14 06:28:01 +00:00
project Move project related info from main Makefile to project dir 2007-08-14 07:45:01 +00:00
target Workaround bug in TinyX makedepend by removing some whitespace 2007-08-13 20:18:25 +00:00
toolchain Fix continous remake's of uClibc, Save .config to .oldconfig before 'conf', cleanup ARM config to avoid stop during build 2007-08-14 07:07:13 +00:00
.defconfig - update defconfig 2007-06-07 12:54:29 +00:00
Config.in Stop halting ARM build to configure uClibc 2007-08-13 20:22:17 +00:00
Makefile Move project related info from main Makefile to project dir 2007-08-14 07:45:01 +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.