Go to file
Yann E. MORIN 61d322c3d2 package/cURL: fix static link whith openSSL
When openSSL is selected, cURL is configured to use it.

But in this case, the libcurl.pc file /forgets/ to require link
against -ldl.

This can happen, for example, when BR2_PREFER_STATIC_LIB is not set,
but an executable wants to be linked statically (for various reasons
which are irrelevant here).

Fix that by appending a 'Requires: openssl' line to libcurl.pc.in,
but only if openSSL is enabled.

As suggested by Arnout, do it in a post-patch hook, rather as a
post-install hook.

Cc: Arnout Vandecappelle <arnout@mind.be>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-12-02 23:21:00 -08:00
arch xtensa: use uppercase for configurations and modified overlay structure 2012-11-21 11:08:50 +01:00
board Add board files for snowball 2012-11-30 07:59:35 -08:00
boot Remove unused barebox 2012.07 string 2012-11-21 11:17:12 +01:00
configs Add config file for the snowball board 2012-11-30 08:02:15 -08:00
docs Update for 2012.11 2012-12-02 16:33:09 -08:00
fs reorder fs alphabetically 2012-12-02 23:19:25 -08:00
linux linux: bump 3.6.x stable version 2012-11-28 13:59:04 -08:00
package package/cURL: fix static link whith openSSL 2012-12-02 23:21:00 -08:00
support Warn the user about the usage of output/target as the root filesystem 2012-11-17 17:12:49 +01:00
system skeleton: add /etc/nsswitch.conf 2012-12-02 16:32:16 -08:00
toolchain Merge branch 'next' 2012-12-02 17:19:40 -08:00
.defconfig
.gitignore
CHANGES Update for 2012.11 2012-12-02 16:33:09 -08:00
Config.in pkg-infra: introduce errors for legacy API 2012-11-30 12:06:40 -08:00
Config.in.legacy legacy: BR2_PACKAGE_LIBINTL is replaced by gettext 2012-11-30 12:07:35 -08:00
COPYING
Makefile Makefile: kickoff 2013.02 cycle 2012-12-02 17:19:18 -08:00
Makefile.legacy legacy: add error target for host-pkg-config 2012-11-30 12:07:09 -08: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 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: buildroot@uclibc.org