docs/manual: mention that custom toolchains is also useful for BR toolchains
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
This commit is contained in:
parent
08ad8a7c04
commit
3883823614
@ -159,14 +159,14 @@ Then, you have three solutions to use an external toolchain:
|
||||
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 and whether it has built-in RPC support. If
|
||||
your external toolchain uses the 'uClibc'
|
||||
useful for toolchains generated using crosstool-NG or with Buildroot
|
||||
itself. 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 and whether it has
|
||||
built-in RPC support. 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
|
||||
|
Loading…
Reference in New Issue
Block a user