Buildroot customized for the GCW0
Makefile C Python Shell C++ Perl Other
Latest commit c314480 Feb 13, 2016 @mthuurne mthuurne Merge pull request #23 from dmitrysmagin/opendingux-2014.05-mikmod-fi…

libmikmod: Fixup prefix= and exec_prefix= in libmikmod-config
Failed to load latest commit information.
board opendingux: Prevent block devices from being mounted to /media/data May 30, 2015
fs fs/tar: use qstrip to clean up build output May 28, 2014
toolchain glibc: doesn't build for PowerPC SPE May 30, 2014
.defconfig buildroot: get rid of s390 support Jan 12, 2009
CHANGES Update for 2014.05 May 31, 2014
COPYING clarify license and fix website license link May 8, 2009
Makefile gdb: Fix on-target threads debugging Jul 2, 2014


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 sort of
    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!

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.

Building out-of-tree:

Buildroot supports building out of tree with a syntax similar
to the Linux kernel. To use it, add O=<directory> to the
make command line, E.G.:

$ make O=/tmp/build

And all the output files (including .config) will be located under /tmp/build.

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 linux-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 the
buildroot mailing list: