Godot's buildroot soft-fork for generating toolchains to make portable Linux releases of Godot games.
Go to file
Ulf Samuelsson f60308be15 Från: Brad House <brad@mainstreetsoftworks.com>
Till: 	buildroot@uclibc.org
Ämne: 	[Buildroot] [patch] libxml2 install fails because of missing directory
Datum: 	Tue, 14 Aug 2007 16:34:34 -0400  (22.34 CEST)

If libxml2 is installed before $(TARGET_DIR)/usr/lib is created,
it fails because it can't copy the library over.

Also, the dependency tree is a bit messed up.  libxml2.a should
only be installed if target-headers is specified, it's 4MB
on my system and the only .a file I found in my TARGET_DIR
(target-headers was not specified).

The attached patch fixes the above problems.

-Brad
2007-08-19 20:59:37 +00:00
docs
package Från: Brad House <brad@mainstreetsoftworks.com> 2007-08-19 20:59:37 +00:00
project
target Update AVR32 tools download location 2007-08-19 18:26:31 +00:00
toolchain Move AVR32 kernel patches to target/device/Atmel/arch-avr32 2007-08-18 08:46:41 +00:00
.defconfig
Config.in
Makefile
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

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.