Go to file
Thomas Petazzoni e014e3da09 cairo: PDF support is needed when SVG support is enabled
As soon as PostScript, PNG or SVG support is enabled, PDF support is
required for Cairo to build properly. Otherwise, you get build
failures such as:

.libs/cairo-type3-glyph-surface.o: In function `_cairo_type3_glyph_surface_set_stream':
/home/thomas/local/buildroot-dl/cairo-1.8.10/src/cairo-type3-glyph-surface.c:337: undefined reference to `_cairo_pdf_operators_set_stream'
/home/thomas/local/buildroot-dl/cairo-1.8.10/src/cairo-type3-glyph-surface.c:337: undefined reference to `_cairo_pdf_operators_set_stream'

Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-07-29 22:18:57 +02:00
boot u-boot: fix custom patch handling 2010-07-29 22:18:56 +02:00
configs toolchain: remove multilib 2010-07-28 23:21:45 +02:00
docs Fix a wrong sentence in the docs. 2010-07-08 22:15:34 +02:00
fs fs: add option to define path to custom rootfs skeleton 2010-07-18 23:15:55 +02:00
linux linux: more mistake detection 2010-07-29 22:18:57 +02:00
package cairo: PDF support is needed when SVG support is enabled 2010-07-29 22:18:57 +02:00
scripts Improvements to the package conversion status script 2010-07-26 22:48:41 +02:00
target toolchain: remove multilib 2010-07-28 23:21:45 +02:00
toolchain gdb: disallow GDB_HOST on external toolchain builds 2010-07-29 16:04:38 +02:00
.defconfig
.gitignore
CHANGES CHANGES: #2257 / #2263 are resolved 2010-07-29 09:10:25 +02:00
Config.in
COPYING
Makefile toolchain: move makefile includes 2010-07-28 16:20:06 +02:00
TODO

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.

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 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 the
buildroot mailing list: buildroot@uclibc.org