From: Thomas Petazzoni Buildroot supports using existing toolchains through a
- mechanism called external toolchain.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:
External binary toolchain
toolchain
- typeExternal toolchain C
- library
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.External toolchain path
- appropriately. It should be set to a path where a bin/ directory
- contains your cross-compiling toolsExternal toolchain prefix
so that the
- prefix, suffixed with -gcc
or -ld
will
- correspond to your cross-compiling toolsToolchain
through the available ones. This is
+ definitely the easiest solution.Toolchain
through the available ones,
+ unselect Download toolchain automatically
, and fill
+ the Toolchain path
text entry with the path to your
+ cross-compiling toolchain.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