From b7b6946b56219c09c72d6fe3f583333f42a2b05c Mon Sep 17 00:00:00 2001 From: Thomas Petazzoni Date: Tue, 28 Apr 2009 20:58:57 +0000 Subject: Documentation cleanups * Add the section describing the project feature to the table of contents * Change the formatting of titles in the section on the project feature * Mention that the section on project feature is obsolete since the feature has now been implemented * Remove the duplication about two different sections documenting basically the same thing : how to use the Buildroot toolchain. --- docs/buildroot.html | 71 ++++++++++++++++++++++------------------------------- 1 file changed, 30 insertions(+), 41 deletions(-) diff --git a/docs/buildroot.html b/docs/buildroot.html index 846abe5b7..ff8c4ca65 100644 --- a/docs/buildroot.html +++ b/docs/buildroot.html @@ -32,9 +32,10 @@
  • Customizing the uClibc configuration
  • How Buildroot works
    • -
  • Using the uClibc toolchain
    • -
  • Using the uClibc toolchain - outside of Buildroot
    • +
    • +
  • Using the uClibc toolchain + outside Buildroot
  • Location of downloaded packages
  • Extending Buildroot with more @@ -524,7 +525,10 @@ $ make me<TAB>

    Building several projects in the same buildroot source tree

    -

    BACKGROUND

    +

    Note: the contents of this section are obsolete since this + feature has been implemented.

    + +

    Background

    Buildroot has always supported building several projects in the same tree if each project was for a different architecture.

    @@ -560,8 +564,7 @@ $ make me<TAB> was also duplicated, so each package would also be rebuilt once per project, resulting in even longer build times.

    - -

    PROJECT TO SHARE TOOLCHAIN AND PACKAGE BUILDS

    +

    Project to share toolchain and package builds

    Work has started on a project which will allow the user to build multiple root file systems for the same architecture in the same tree. @@ -591,7 +594,7 @@ $ make me<TAB>

    Only packages, not used by the first project, will have to go through the normal extract-configure-compile flow.

    -

    IMPLEMENTATION

    +

    Implementation

    The core of the solution is the introduction of two new directories:

    @@ -646,7 +649,7 @@ $ make me<TAB>

    The resulting binaries for all architectures are stored in the "$(BINARIES_DIR)" directory.

    -

    SUMMARY

    +

    Summary

    The project will share directories which can be share without conflicts, but will use unique build directories, where the user @@ -693,7 +696,7 @@ $ make me<TAB> defaults to "make menuconfig".

    -

    Todo

    +

    Todo

    1. Configurable packages
      2. @@ -763,7 +766,7 @@ $ make me<TAB>

    Using the - uClibc toolchain

    + uClibc toolchain outside Buildroot

    You may want to compile your own programs or other software that are not packaged in Buildroot. In order to do this, you can @@ -791,32 +794,19 @@ export PATH="$PATH:~/buildroot/build_mips/staging_dir/usr/bin/" mips-linux-gcc -o foo foo.c -

    Important : do not try to move a gcc-3.x toolchain to an other - directory, it won't work. There are some hardcoded paths in the - gcc configuration. If the default toolchain directory - doesn't suit your needs, please refer to the Using the uClibc toolchain outside of - buildroot section.

    -

    If you are using a current gcc-4.x, then use --sysroot and -isysroot - since these toolchains have fully functional sysroot support. No - hardcoded paths do exist in these configurations.

    - -

    Using the - uClibc toolchain outside of buildroot

    - -

    By default, the cross-compilation toolchain is generated inside - build_ARCH/staging_dir/. But sometimes, it may be useful to - install it somewhere else, so that it can be used to compile other programs - or by other users. Moving the build_ARCH/staging_dir/ - directory elsewhere is not possible if using gcc-3.x, because there - are some hardcoded paths in the toolchain configuration. This works, thanks - to sysroot support, with current, stable gcc-4.x toolchains, of course.

    - -

    If you want to use the generated gcc-3.x toolchain for other purposes, - you can configure Buildroot to generate it elsewhere using the - option of the configuration tool : Build options -> - Toolchain and header file location, which defaults to - $(BUILD_DIR)/staging_dir/.

    +

    Important : do not try to move a gcc-3.x toolchain to an other + directory, it won't work. There are some hardcoded paths in the + gcc configuration. If you are using a current gcc-4.x, it + is possible to relocate the toolchain, but then + --sysroot must be passed every time the compiler is + called to tell where the libraries and header files are, which + might be cumbersome.

    + +

    It is also possible to generate the Buildroot toolchain in + another directory than build_ARCH/staging_dir using + the Build options -> Toolchain and header file + location option. This could be useful if the toolchain + must be shared with other users.

    Location of downloaded packages

    @@ -1173,13 +1163,12 @@ endif
  • http://www.uclibc.org/
  • http://www.busybox.net/
    • - -- cgit v1.2.3