mirror of
https://gitlab.com/buildroot.org/buildroot.git
synced 2026-09-10 16:24:17 -09:00
7f8fa1afeb
This commit reworks the build and install steps of the olsr package,
to fix a number of problems and do minor improvements:
1. The build step was doing "make <foo>" for each
plugin. Unfortunately, inside olsr build system, doing "make
<foo>" for a plugin triggers a clean of the plugin directory, a
build, and then an installation of the plugin. This installation
fails because DESTDIR is not passed at the install step. This
leads to build issues like
http://autobuild.buildroot.org/results/a9fed78cd0b3991763a797c38387edd4157fbdb9/build-end.log. To
fix this, we call make in each plugin's directory, which is what
"make <foo>" was doing internally.
2. The install step was manually installing the olsrd binary. We now
instead use the install_bin make target that comes in olsr's build
system.
3. The install step was manually installing the olsr plugins. We now
instead use the install make target available in each plugin's
makefile.
4. We use 'install' to install the init script, which avoids the
manual creation of /etc/init.d.
5. We use 'install' to install the sample configuration file.
6. We remove the useless strip commands.
7. We add a patch that allows us to pass LDCONFIG=/bin/true to avoid
ldconfig being called during the installation process.
8. We remove commands from the clean step that were in fact
uninstallation commands. We don't bother re-adding those commands
in an uninstallation step, since it is now generally accepted that
the uninstall step is quite useless and should be deprecated.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
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