Go to file
Hans-Christian Egtvedt 7108decafe doom-wad: split out and fix installation of Doom shareware wad file
This patch splits the installation of the shareware WAD file into a separate
package. The wad file will also be installed into /usr/share/games/doom
directory, since the client will search this directory when starting.

The Makefile rule has also been altered to use tools defined by Buildroot to
extract and install the wad file. The package is also multiple project safe
now.

Signed-off-by: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
2008-09-24 12:53:45 +00:00
docs buildroot: support out-of-tree builds 2008-08-31 20:23:47 +00:00
package doom-wad: split out and fix installation of Doom shareware wad file 2008-09-24 12:53:45 +00:00
project Makefile: support relative paths for out of tree builds 2008-09-16 20:53:45 +00:00
scripts Kconfig: remove 'default n' 2008-07-17 20:01:44 +00:00
target target/linux/advanced: don't hardcode date suffix 2008-09-22 12:04:05 +00:00
toolchain Applied change from Ben Nizette and Hans-Christian Egtvedt to 2008-09-04 02:30:56 +00:00
.defconfig defconfig: remove settings with default values 2008-04-04 07:12:42 +00:00
Config.in Config.in: Don't special case atmel targets for image suffix 2008-09-18 09:22:41 +00:00
Makefile Applied patch from Brian Foster <brian.foster@innova-card.com>: 2008-09-11 02:22:47 +00:00
TODO - mark the autotools.in part as taken 2007-09-28 20:52:09 +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

And you can specify a config-file for busybox:
$ make BUSYBOX_CONFIG_FILE=/my/busybox.config

To use a non-standard 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.