6c492d5e7b
Instead of letting the user define all the details of his external toolchain, we define a set of profiles for well-known external toolchains (CodeSourcery ones only at the moment, can easily be extended with other toolchains). Once a profile has been choosen, the user is offered the choice of either letting Buildroot download and install the external toolchain, or (as before) to tell Buildroot where the toolchain is installed on the system. We of course provide a "custom profile", through which the user can configure Buildroot to use a custom external toolchain for which no profile is available. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
38 lines
1.0 KiB
Plaintext
38 lines
1.0 KiB
Plaintext
menu "Toolchain"
|
|
choice
|
|
prompt "Toolchain type"
|
|
help
|
|
Select whether to use the toolchain provided by buildroot
|
|
or an external toolchain.
|
|
|
|
Some vendors provide toolchains in binary form, some in
|
|
source form.
|
|
|
|
config BR2_TOOLCHAIN_BUILDROOT
|
|
bool "Buildroot toolchain"
|
|
|
|
config BR2_TOOLCHAIN_EXTERNAL
|
|
bool "External toolchain"
|
|
help
|
|
Select if you want to use an existing cross-compiling
|
|
toolchain. Buildroot can either download automatically a
|
|
toolchain, or use an already installed toolchain.
|
|
|
|
config BR2_TOOLCHAIN_CTNG
|
|
bool "Crosstool-NG toolchain"
|
|
help
|
|
Say 'y' if you want to generate the toolchain with crosstool-NG
|
|
( http://ymorin.is-a-geek.org/projects/crosstool )
|
|
|
|
This is considered experimental, and you can expect some breakage.
|
|
|
|
endchoice
|
|
|
|
source "toolchain/toolchain-buildroot/Config.in"
|
|
source "toolchain/toolchain-external/Config.in"
|
|
source "toolchain/toolchain-crosstool-ng/Config.in"
|
|
source "toolchain/toolchain-common.in"
|
|
source "toolchain/toolchain-buildroot/Config.in.2"
|
|
|
|
endmenu
|