1 menu "Toolchain options"
3 comment "General toolchain options"
7 prompt "Use sysroot'ed toolchain"
10 Use the 'shinny new' sysroot feature of gcc: libraries split between
11 prefix/target/sys-root/lib and prefix/target/sys-root/usr/lib
13 You definitely want to say 'Y' here. Yes you do. I know you do. Say 'Y'.
17 prompt "Build shared libraries"
20 Say 'y' here, unless you don't want shared libraries.
22 You might not want shared librries if you're building for a target that
23 don't support it (maybe some nommu targets, for example, or bare metal).
27 prompt "Threading implentation to use:"
28 default THREADS_NPTL if LIBC_SUPPORT_NPTL
29 default THREADS_LINUXTHREADS if LIBC_SUPPORT_LINUXTHREADS && ! LIBC_SUPPORT_NPTL
30 default THREADS_NONE if ! LIBC_SUPPORT_LINUXTHREADS && ! LIBC_SUPPORT_NPTL
35 depends on LIBC_SUPPORT_NPTL
37 config THREADS_LINUXTHREADS
40 depends on LIBC_SUPPORT_LINUXTHREADS
50 default "nptl" if THREADS_NPTL
51 default "linuxthreads" if THREADS_LINUXTHREADS
52 default "none" if THREADS_NONE
54 config TARGET_MULTILIB
56 # prompt "Enable 'multilib' support (EXPERIMENTAL)"
59 Enable the so-called 'multilib' support.
61 With the same toolchain, and on some architectures, you will be able to
62 build big and little endian binaries, soft- and hard-float, etc...
64 See the gcc configure manual at http://gcc.gnu.org/install/configure.html
65 to see what multilib your target supports.
67 It's preferable for now to build two (or more) toolchains, one for each
68 configuration you need to support (eg. one for thumb and one for ARM,
69 etc...). You can use the vendor string to diferentiate those toolchains.
73 prompt "Vendor string"
76 Vendor part of the machine triplet.
78 A triplet is of the form arch-vendor-kernel-system.
79 You can set the second part, vendor, to whatever you see fit.
80 Use a single word, or use underscores "_" to separate words.
82 Keep the default (unkown) if you don't know better.
89 Normaly, you'd call your toolchain component (especially gcc) by
90 prefixing the target triplet followed by a dash and the component name
91 (eg. armeb-unknown-linux-uclibc-gcc).
93 You can enter a shortcut here. This string will be used to create
94 symbolic links to the toolchain tools (eg. if you enter "foo-bar" here,
95 then gcc for your toolchain will also be available as "foo-bar-gcc" along
96 with the original name).
98 You shouldn't need to enter anything here, unless you plan to manually
99 call the tools (autotools-based ./configure will use the standard name).
101 comment "Toolchain type"
110 prompt "Native (EXPERIMENTAL)"
111 depends on EXPERIMENTAL
113 Build a native toolchain.
114 See docs/overview.txt
120 Build a cross-toolchain.
121 See docs/overview.txt
125 prompt "Croos-native (EXPERIMENTAL)"
126 depends on EXPERIMENTAL
128 Build a cross-native toolchain.
129 See docs/overview.txt
133 prompt "Canadian (EXPERIMENTAL)"
134 depends on EXPERIMENTAL
136 Build a canadian-toolchain.
137 See docs/overview.txt
141 config TOOLCHAIN_TYPE
143 default "native" if NATIVE
144 default "cross" if CROSS
145 default "cross-native" if CROSS_NATIVE
146 default "canadian" if CANADIAN
150 prompt "Build system triplet"
153 Canonical name of the machine building the toolchain.
154 You should leave empty, unless you really now what you're doing.
161 The native C compiler.
163 You can set this to an alternative compiler if you have more than one
164 installed (eg. gcc is gcc-4.1.1 and you want to use gcc-3.4.6).
166 You can leave this empty as well, in which case gcc will be used.
170 prompt "Host system triplet"
172 depends on NATIVE || CANADIAN
174 Canonical name of the machine running the toolchain.
178 prompt "Cross-compiler prefix for host system"
179 default "${CT_HOST}-"
180 depends on NATIVE || CANADIAN
182 C compiler targeting the host system.
186 prompt "Cross-compiler prefix for target system"
187 default "${CT_TARGET}-"
190 C compiler targeting the target system.