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"
18 depends on ! BARE_METAL
21 Say 'y' here, unless you don't want shared libraries.
23 You might not want shared libraries if you're building for a target that
24 don't support it (maybe some nommu targets, for example, or bare metal).
28 prompt "Vendor string"
31 Vendor part of the target tuple.
33 A tuple is of the form arch-vendor-kernel-system.
34 You can set the second part, vendor, to whatever you see fit.
35 Use a single word, or use underscores "_" to separate words.
37 Keep the default (unkown) if you don't know better.
39 config TARGET_ALIAS_SED_EXPR
41 prompt "Target sed transform"
44 Normaly, you'd call your toolchain components (especially gcc) by
45 prefixing the target tuple followed by a dash and the component name
46 (eg. armeb-unknown-linux-uclibc-gcc).
48 You can enter here a sed expression to be applied to ${CT_TARGET} to
49 create an alias for your toolchain.
51 For example, "s/${CT_TARGET_VENDOR}/foobar/" (without the double quotes)
52 will create the armeb-foobar-linux-uclibc alias to the above-mentioned
55 You shouldn't need to enter anything here, unless you plan to manually
56 call the tools (autotools-based ./configure will use the standard name).
63 Normaly, you'd call your toolchain components (especially gcc) by
64 prefixing the target tuple followed by a dash and the component name
65 (eg. armeb-unknown-linux-uclibc-gcc).
67 You can enter a shortcut here. This string will be used to create
68 symbolic links to the toolchain tools (eg. if you enter "foo-bar" here,
69 then gcc for your toolchain will also be available as "foo-bar-gcc" along
70 with the original name).
72 You shouldn't need to enter anything here, unless you plan to manually
73 call the tools (autotools-based ./configure will use the standard name).
75 comment "Toolchain type"
84 prompt "Native (NO CODE!) (EXPERIMENTAL)"
85 depends on EXPERIMENTAL
87 Build a native toolchain.
94 Build a cross-toolchain.
99 prompt "Cross-native (NO CODE!) (EXPERIMENTAL)"
100 depends on EXPERIMENTAL
102 Build a cross-native toolchain.
103 See docs/overview.txt
107 prompt "Canadian (NO CODE!) (EXPERIMENTAL)"
108 depends on EXPERIMENTAL
110 Build a canadian-toolchain.
111 See docs/overview.txt
115 config TOOLCHAIN_TYPE
117 default "native" if NATIVE
118 default "cross" if CROSS
119 default "cross-native" if CROSS_NATIVE
120 default "canadian" if CANADIAN
122 comment "Build system"
126 prompt "| Tuple (READ HELP!)"
129 Canonical name of the machine building the toolchain.
130 You should leave empty, unless you really now what you're doing.
134 prompt "| Tools prefix (READ HELP!)"
137 If you have your *build system* tools in a weird location, and/or
138 they have an unusual prefix, enter it here.
140 Usually, you should leave that empty!
143 If your *build* gcc is /opt/build-tools/bin/weird-gcc then you
145 /opt/build-tools/bin/weird-
147 If your *build* gcc is /opt/build-tools/bin/weird-gcc and
148 /opt/build-tools/bin is in your PATH, you should enter:
151 If your *build* gcc is /opt/build-tools/bin/gcc then you
152 should enter (do not forget to add the trailing '/'):
153 /opt/build-tools/bin/
157 prompt "| Tools suffix (READ HELP!)"
160 If your *build system* tools have an unusual suffix, enter it
163 Usually, you should leave that empty!
166 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
167 installed as gcc-3.4, then you should enter:
170 It can happen that some of the tools have a suffix, when others
171 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
172 for that by checking the tools without the suffix in case it can
173 not find some of the tool.
177 comment "Host system"
181 prompt "| Tuple (READ HELP!)"
184 Canonical name of the machine running the toolchain.
188 prompt "| Tools prefix (READ HELP!)"
191 If you have your *host system* tools in a weird location, and/or
192 they have an unusual prefix, enter it here.
194 Usually, you should leave that empty!
197 If your *host* gcc is /opt/host-tools/bin/weird-gcc then you
199 /opt/host-tools/bin/weird-
201 If your *host* gcc is /opt/host-tools/bin/weird-gcc and
202 /opt/host-tools/bin is in your PATH, you should enter:
205 If your *host* gcc is /opt/host-tools/bin/gcc then you
206 should enter (do not forget to add the trailing '/'):
211 prompt "| Tools suffix (READ HELP!)"
214 If your *host system* tools have an unusual suffix, enter it
217 Usually, you should leave that empty!
220 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
221 installed as gcc-3.4, then you should enter:
224 It can happen that some of the tools have a suffix, when others
225 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
226 for that by checking the tools without the suffix in case it can
227 not find some of the tool.
231 if CROSS_NATIVE || CANADIAN
233 comment "Target system"
237 prompt "| Tools prefix (READ HELP!)"
240 If you have your *target system* tools in a weird location, and/or
241 they have an unusual prefix, enter it here.
243 Usually, you should leave that empty!
246 If your *target* gcc is /opt/target-tools/bin/weird-gcc then you
248 /opt/target-tools/bin/weird-
250 If your *target* gcc is /opt/target-tools/bin/weird-gcc and
251 /opt/target-tools/bin is in your PATH, you should enter:
254 If your *target* gcc is /opt/target-tools/bin/gcc then you
255 should enter (do not forget to add the trailing '/'):
256 /opt/target-tools/bin/
260 prompt "| Tools suffix (READ HELP!)"
263 If your *target system* tools have an unusual suffix, enter it
266 Usually, you should leave that empty!
269 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
270 installed as gcc-3.4, then you should enter:
273 It can happen that some of the tools have a suffix, when others
274 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
275 for that by checking the tools without the suffix in case it can
276 not find some of the tool.
278 endif # CROSS_NATIVE || CANADIAN