Godot's buildroot soft-fork for generating toolchains to make portable Linux releases of Godot games.
Go to file
Hans-Christian Egtvedt 0915c62d98 sdl_net: fix install options for target and staging
This patch install with install-strip to the target and uses the default for
installing to staging. Makes the makefile even more compact, and also more
correct with using install-strip to get proper stripping of the installed
library.

Signed-off-by: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
2008-09-25 06:13:24 +00:00
docs
package sdl_net: fix install options for target and staging 2008-09-25 06:13:24 +00:00
project Makefile: support relative paths for out of tree builds 2008-09-16 20:53:45 +00:00
scripts
target target/linux/advanced: don't hardcode date suffix 2008-09-22 12:04:05 +00:00
toolchain
.defconfig
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

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