2007-04-17 22:24:42 +00:00
|
|
|
menu "Toolchain options"
|
|
|
|
|
|
|
|
comment "General toolchain options"
|
|
|
|
|
|
|
|
config USE_SYSROOT
|
|
|
|
bool
|
|
|
|
prompt "Use sysroot'ed toolchain"
|
|
|
|
default y
|
|
|
|
help
|
|
|
|
Use the 'shinny new' sysroot feature of gcc: libraries split between
|
|
|
|
prefix/target/sys-root/lib and prefix/target/sys-root/usr/lib
|
|
|
|
|
|
|
|
You definitely want to say 'Y' here. Yes you do. I know you do. Say 'Y'.
|
|
|
|
|
|
|
|
config SHARED_LIBS
|
|
|
|
bool
|
|
|
|
prompt "Build shared libraries"
|
|
|
|
default y
|
|
|
|
help
|
|
|
|
Say 'y' here, unless you don't want shared libraries.
|
|
|
|
|
|
|
|
You might not want shared librries if you're building for a target that
|
|
|
|
don't support it (maybe some nommu targets, for example, or bare metal).
|
|
|
|
|
2007-05-29 19:30:38 +00:00
|
|
|
choice
|
|
|
|
bool
|
2008-02-14 22:44:34 +00:00
|
|
|
prompt "Threading implementation to use:"
|
2007-05-29 19:30:38 +00:00
|
|
|
default THREADS_NPTL if LIBC_SUPPORT_NPTL
|
|
|
|
default THREADS_LINUXTHREADS if LIBC_SUPPORT_LINUXTHREADS && ! LIBC_SUPPORT_NPTL
|
|
|
|
default THREADS_NONE if ! LIBC_SUPPORT_LINUXTHREADS && ! LIBC_SUPPORT_NPTL
|
|
|
|
|
|
|
|
config THREADS_NPTL
|
|
|
|
bool
|
|
|
|
prompt "nptl"
|
|
|
|
depends on LIBC_SUPPORT_NPTL
|
|
|
|
|
|
|
|
config THREADS_LINUXTHREADS
|
|
|
|
bool
|
|
|
|
prompt "linuxthreads"
|
|
|
|
depends on LIBC_SUPPORT_LINUXTHREADS
|
|
|
|
|
|
|
|
config THREADS_NONE
|
|
|
|
bool
|
|
|
|
prompt "none"
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
|
|
config THREADS
|
|
|
|
string
|
|
|
|
default "nptl" if THREADS_NPTL
|
|
|
|
default "linuxthreads" if THREADS_LINUXTHREADS
|
|
|
|
default "none" if THREADS_NONE
|
|
|
|
|
2007-04-17 22:24:42 +00:00
|
|
|
config TARGET_VENDOR
|
|
|
|
string
|
|
|
|
prompt "Vendor string"
|
|
|
|
default "unknown"
|
|
|
|
help
|
2007-08-15 16:18:35 +00:00
|
|
|
Vendor part of the target tuple.
|
2007-04-17 22:24:42 +00:00
|
|
|
|
2007-08-15 16:18:35 +00:00
|
|
|
A tuple is of the form arch-vendor-kernel-system.
|
2007-04-17 22:24:42 +00:00
|
|
|
You can set the second part, vendor, to whatever you see fit.
|
|
|
|
Use a single word, or use underscores "_" to separate words.
|
|
|
|
|
|
|
|
Keep the default (unkown) if you don't know better.
|
|
|
|
|
2007-08-07 19:40:38 +00:00
|
|
|
config TARGET_ALIAS_SED_EXPR
|
|
|
|
string
|
|
|
|
prompt "Target sed transform"
|
|
|
|
default ""
|
|
|
|
help
|
|
|
|
Normaly, you'd call your toolchain components (especially gcc) by
|
2007-08-15 16:18:35 +00:00
|
|
|
prefixing the target tuple followed by a dash and the component name
|
2007-08-07 19:40:38 +00:00
|
|
|
(eg. armeb-unknown-linux-uclibc-gcc).
|
|
|
|
|
|
|
|
You can enter here a sed expression to be applied to ${CT_TARGET} to
|
|
|
|
create an alias for your toolchain.
|
|
|
|
|
|
|
|
For example, "s/${CT_TARGET_VENDOR}/foobar/" (without the double quotes)
|
|
|
|
will create the armeb-foobar-linux-uclibc alias to the above-mentioned
|
|
|
|
toolchain.
|
|
|
|
|
|
|
|
You shouldn't need to enter anything here, unless you plan to manually
|
|
|
|
call the tools (autotools-based ./configure will use the standard name).
|
|
|
|
|
2007-04-17 22:24:42 +00:00
|
|
|
config TARGET_ALIAS
|
|
|
|
string
|
|
|
|
prompt "Target alias"
|
|
|
|
default ""
|
|
|
|
help
|
2007-08-07 19:40:38 +00:00
|
|
|
Normaly, you'd call your toolchain components (especially gcc) by
|
2007-08-15 16:18:35 +00:00
|
|
|
prefixing the target tuple followed by a dash and the component name
|
2007-04-17 22:24:42 +00:00
|
|
|
(eg. armeb-unknown-linux-uclibc-gcc).
|
|
|
|
|
|
|
|
You can enter a shortcut here. This string will be used to create
|
|
|
|
symbolic links to the toolchain tools (eg. if you enter "foo-bar" here,
|
|
|
|
then gcc for your toolchain will also be available as "foo-bar-gcc" along
|
|
|
|
with the original name).
|
|
|
|
|
|
|
|
You shouldn't need to enter anything here, unless you plan to manually
|
|
|
|
call the tools (autotools-based ./configure will use the standard name).
|
|
|
|
|
|
|
|
comment "Toolchain type"
|
|
|
|
|
|
|
|
choice
|
|
|
|
bool
|
|
|
|
prompt "Type"
|
|
|
|
default CROSS
|
|
|
|
|
|
|
|
config NATIVE
|
|
|
|
bool
|
|
|
|
prompt "Native (EXPERIMENTAL)"
|
|
|
|
depends on EXPERIMENTAL
|
|
|
|
help
|
|
|
|
Build a native toolchain.
|
|
|
|
See docs/overview.txt
|
|
|
|
|
|
|
|
config CROSS
|
|
|
|
bool
|
|
|
|
prompt "Cross"
|
|
|
|
help
|
|
|
|
Build a cross-toolchain.
|
|
|
|
See docs/overview.txt
|
|
|
|
|
|
|
|
config CROSS_NATIVE
|
|
|
|
bool
|
2008-02-14 22:44:34 +00:00
|
|
|
prompt "Cross-native (EXPERIMENTAL)"
|
2007-04-17 22:24:42 +00:00
|
|
|
depends on EXPERIMENTAL
|
|
|
|
help
|
|
|
|
Build a cross-native toolchain.
|
|
|
|
See docs/overview.txt
|
|
|
|
|
|
|
|
config CANADIAN
|
|
|
|
bool
|
|
|
|
prompt "Canadian (EXPERIMENTAL)"
|
|
|
|
depends on EXPERIMENTAL
|
|
|
|
help
|
|
|
|
Build a canadian-toolchain.
|
|
|
|
See docs/overview.txt
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
2007-05-17 16:22:51 +00:00
|
|
|
config TOOLCHAIN_TYPE
|
|
|
|
string
|
|
|
|
default "native" if NATIVE
|
|
|
|
default "cross" if CROSS
|
|
|
|
default "cross-native" if CROSS_NATIVE
|
|
|
|
default "canadian" if CANADIAN
|
|
|
|
|
2007-04-17 22:24:42 +00:00
|
|
|
config BUILD
|
|
|
|
string
|
2007-08-15 16:18:35 +00:00
|
|
|
prompt "Build system tuple"
|
2007-04-17 22:24:42 +00:00
|
|
|
default ""
|
|
|
|
help
|
|
|
|
Canonical name of the machine building the toolchain.
|
|
|
|
You should leave empty, unless you really now what you're doing.
|
|
|
|
|
|
|
|
config CC_NATIVE
|
|
|
|
string
|
|
|
|
prompt "Native gcc"
|
|
|
|
default "gcc"
|
|
|
|
help
|
|
|
|
The native C compiler.
|
|
|
|
|
|
|
|
You can set this to an alternative compiler if you have more than one
|
|
|
|
installed (eg. gcc is gcc-4.1.1 and you want to use gcc-3.4.6).
|
|
|
|
|
|
|
|
You can leave this empty as well, in which case gcc will be used.
|
|
|
|
|
|
|
|
config HOST
|
|
|
|
string
|
2007-08-15 16:18:35 +00:00
|
|
|
prompt "Host system tuple"
|
2007-04-17 22:24:42 +00:00
|
|
|
default ""
|
|
|
|
depends on NATIVE || CANADIAN
|
|
|
|
help
|
|
|
|
Canonical name of the machine running the toolchain.
|
|
|
|
|
|
|
|
config HOST_CC
|
|
|
|
string
|
|
|
|
prompt "Cross-compiler prefix for host system"
|
|
|
|
default "${CT_HOST}-"
|
|
|
|
depends on NATIVE || CANADIAN
|
|
|
|
help
|
|
|
|
C compiler targeting the host system.
|
|
|
|
|
|
|
|
config TARGET_CC
|
|
|
|
string
|
|
|
|
prompt "Cross-compiler prefix for target system"
|
|
|
|
default "${CT_TARGET}-"
|
|
|
|
depends on CANADIAN
|
|
|
|
help
|
|
|
|
C compiler targeting the target system.
|
|
|
|
|
|
|
|
endmenu
|