From: Thomas Petazzoni Date: Sun, 30 Jan 2011 14:37:46 +0000 (+0100) Subject: Update documentation about external toolchain X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=7af45b8ae07cce97c6f72245c13fbeb355eeaea5;p=buildroot.git Update documentation about external toolchain Reword the documentation on external toolchain to take into account the new features added since 2010.11 concerning external toolchain profiles. Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard --- diff --git a/docs/buildroot.html b/docs/buildroot.html index 3a7684d30f..6226c1166c 100644 --- a/docs/buildroot.html +++ b/docs/buildroot.html @@ -706,31 +706,48 @@ $(ZLIB_DIR)/libz.a: $(ZLIB_DIR)/.configured

Buildroot supports using existing toolchains through a - mechanism called external toolchain.

+ mechanism called external toolchain. The external toolchain + mechanism is enabled in the Toolchain menu, by + selecting External toolchain in Toolchain + type.

-

To enable the use of an external toolchain, go to the - Toolchain menu, and :

+

Then, you have three solutions to use an external + toolchain:

    -
  • Select the External binary toolchain toolchain - type
  • -
  • Select the appropriate External toolchain C - library
  • -
  • Select the appropriate values for Enable large - file, Enable IPv6, Enable - RPC, Enable toolchain - locale/i18n, Enable WCHAR, Enable - program invocation, Build/install c++ compiler and - libstdc++, according to the configuration of your - external toolchain. Buildroot will check those values at the - beginning of the compilation process and will tell you if you - used incorrect values.
  • -
  • Adjust the External toolchain path - appropriately. It should be set to a path where a bin/ directory - contains your cross-compiling tools
  • -
  • Adjust the External toolchain prefix so that the - prefix, suffixed with -gcc or -ld will - correspond to your cross-compiling tools
  • + +
  • Use a predefined external toolchain profile, and let + Buildroot download, extract and install the toolchain. Buildroot + already knows about a few CodeSourcery toolchains for ARM, + PowerPC, MIPS and SuperH. Just select the toolchain profile + in Toolchain through the available ones. This is + definitely the easiest solution.
  • + +
  • Use a predefined external toolchain profile, but instead of + having Buildroot download and extract the toolchain, you can + tell Buildroot where your toolchain is already installed on your + system. Just select the toolchain profile + in Toolchain through the available ones, + unselect Download toolchain automatically, and fill + the Toolchain path text entry with the path to your + cross-compiling toolchain.
  • + +
  • Use a completely custom external toolchain. This is + particularly useful for toolchains generated using + Crosstool-NG. To do this, select the Custom + toolchain solution in the Toolchain + list. You need to fill the Toolchain + path, Toolchain prefix and External + toolchain C library options. Then, you have to tell + Buildroot what your external toolchain supports. If your + external toolchain uses the glibc library, you only have + to tell whether your toolchain supports C++ or not. If your + external toolchain uses the uclibc library, then you have + to tell Buildroot if it supports largefile, IPv6, RPC, + wide-char, locale, program invocation, threads and C++. At the + beginning of the execution, Buildroot will tell you if the + selected options do not match the toolchain configuration.
  • +

Our external toolchain support has been tested with toolchains