1 menu "Toolchain options"
3 comment "General toolchain options"
12 prompt "Use sysroot'ed toolchain"
15 Use the 'shinny new' sysroot feature of gcc: libraries split between
16 prefix/target/sysroot/lib and prefix/target/sysroot/usr/lib
18 You definitely want to say 'Y' here. Yes you do. I know you do. Say 'Y'.
22 prompt "sysroot directory name" if ! BACKEND
23 depends on USE_SYSROOT
26 Enter the base name of the sysroot directory. Usually, this simply
27 is 'sysroot' (the default) or 'sys-root'.
29 You are free to enter anything here, except for spaces, and '/'
30 (see SYSROOT_DIR_PREFIX, below). If you leave this empy, then the
31 default 'sysroot' is used.
33 config SYSROOT_DIR_PREFIX
35 prompt "sysroot prefix dir (READ HELP)" if ! BACKEND
36 depends on USE_SYSROOT
40 * Unless you realy know you need that, leave it empty!
43 This string will be interpreted as a directory component to be added
44 to the sysroot path, just before the actual sysroot directory.
46 In fact, the sysroot path is constructed as:
47 ${CT_PREFIX_DIR}/${CT_TARGET}/${CT_SYSROOT_DIR_PREFIX}/${CT_SYSROOT_NAME}
49 config STATIC_TOOLCHAIN
51 prompt "Build Static Toolchain (EXPERIMENTAL)"
52 depends on EXPERIMENTAL
54 Build static host binaries.
56 If you wish to move the toolchain to another host, and you are not
57 confident that this host has the required versions of system libs, then
58 you can say 'Y' here, and all the host tools will be linked staticaly.
60 The impacted tools are:
64 The default is 'N', to build dynamicaly-linked host binaries.
66 NOTE: this has no connection to whether the target libraries will be
67 dynamic or static. This only applies to the tools themselves.
69 comment "Tuple completion and aliasing"
73 prompt "Tuple's vendor string"
76 Vendor part of the target tuple.
78 A tuple 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.
81 Use neither dash nor space, as it breaks things.
83 Keep the default (unknown) if you don't know better.
85 config TARGET_ALIAS_SED_EXPR
87 prompt "Tuple's sed transform"
90 Normaly, you'd call your toolchain components (especially gcc) by
91 prefixing the target tuple followed by a dash and the component name
92 (eg. armeb-unknown-linux-uclibc-gcc).
94 You can enter here a sed expression to be applied to ${CT_TARGET} to
95 create an alias for your toolchain.
97 For example, "s/${CT_TARGET_VENDOR}/foobar/" (without the double quotes)
98 will create the armeb-foobar-linux-uclibc alias to the above-mentioned
101 You shouldn't need to enter anything here, unless you plan to manually
102 call the tools (autotools-based ./configure will use the standard name).
106 prompt "Tuple's alias"
109 Normaly, you'd call your toolchain components (especially gcc) by
110 prefixing the target tuple followed by a dash and the component name
111 (eg. armeb-unknown-linux-uclibc-gcc).
113 You can enter a shortcut here. This string will be used to create
114 symbolic links to the toolchain tools (eg. if you enter "foo-bar" here,
115 then gcc for your toolchain will also be available as "foo-bar-gcc" along
116 with the original name).
118 You shouldn't need to enter anything here, unless you plan to manually
119 call the tools (autotools-based ./configure will use the standard name).
121 comment "Toolchain type"
130 prompt "Native (NO CODE!) (EXPERIMENTAL)"
131 depends on EXPERIMENTAL
133 Build a native toolchain.
134 See: "docs/6 - Toolchain types.txt"
140 Build a cross-toolchain.
141 See: "docs/6 - Toolchain types.txt"
145 prompt "Cross-native (NO CODE!) (EXPERIMENTAL)"
146 depends on EXPERIMENTAL
148 Build a cross-native toolchain.
149 See: "docs/6 - Toolchain types.txt"
153 prompt "Canadian (EXPERIMENTAL)"
154 depends on EXPERIMENTAL
156 Build a canadian-toolchain.
157 See: "docs/6 - Toolchain types.txt"
161 config TOOLCHAIN_TYPE
163 default "native" if NATIVE
164 default "cross" if CROSS
165 default "cross-native" if CROSS_NATIVE
166 default "canadian" if CANADIAN
168 comment "Build system"
172 prompt "| Tuple (READ HELP!)"
175 Canonical name of the machine building the toolchain.
176 You should leave empty, unless you really now what you're doing.
180 prompt "| Tools prefix (READ HELP!)"
183 If you have your *build system* tools in a weird location, and/or
184 they have an unusual prefix, enter it here.
186 Usually, you should leave that empty!
189 If your *build* gcc is /opt/build-tools/bin/weird-gcc then you
191 /opt/build-tools/bin/weird-
193 If your *build* gcc is /opt/build-tools/bin/weird-gcc and
194 /opt/build-tools/bin is in your PATH, you should enter:
197 If your *build* gcc is /opt/build-tools/bin/gcc then you
198 should enter (do not forget to add the trailing '/'):
199 /opt/build-tools/bin/
203 prompt "| Tools suffix (READ HELP!)"
206 If your *build system* tools have an unusual suffix, enter it
209 Usually, you should leave that empty!
212 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
213 installed as gcc-3.4, then you should enter:
216 It can happen that some of the tools have a suffix, when others
217 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
218 for that by checking the tools without the suffix in case it can
219 not find some of the tool.
223 comment "Host system"
227 prompt "| Tuple (READ HELP!)"
230 Canonical name of the machine running the toolchain.
234 prompt "| Tools prefix (READ HELP!)"
237 If you have your *host system* tools in a weird location, and/or
238 they have an unusual prefix, enter it here.
240 Usually, you should leave that empty!
243 If your *host* gcc is /opt/host-tools/bin/weird-gcc then you
245 /opt/host-tools/bin/weird-
247 If your *host* gcc is /opt/host-tools/bin/weird-gcc and
248 /opt/host-tools/bin is in your PATH, you should enter:
251 If your *host* gcc is /opt/host-tools/bin/gcc then you
252 should enter (do not forget to add the trailing '/'):
257 prompt "| Tools suffix (READ HELP!)"
260 If your *host system* tools have an unusual suffix, enter it
263 Usually, you should leave that empty!
266 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
267 installed as gcc-3.4, then you should enter:
270 It can happen that some of the tools have a suffix, when others
271 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
272 for that by checking the tools without the suffix in case it can
273 not find some of the tool.
277 if CROSS_NATIVE || CANADIAN
279 comment "Target system"
283 prompt "| Tools prefix (READ HELP!)"
286 If you have your *target system* tools in a weird location, and/or
287 they have an unusual prefix, enter it here.
289 Usually, you should leave that empty!
292 If your *target* gcc is /opt/target-tools/bin/weird-gcc then you
294 /opt/target-tools/bin/weird-
296 If your *target* gcc is /opt/target-tools/bin/weird-gcc and
297 /opt/target-tools/bin is in your PATH, you should enter:
300 If your *target* gcc is /opt/target-tools/bin/gcc then you
301 should enter (do not forget to add the trailing '/'):
302 /opt/target-tools/bin/
306 prompt "| Tools suffix (READ HELP!)"
309 If your *target system* tools have an unusual suffix, enter it
312 Usually, you should leave that empty!
315 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
316 installed as gcc-3.4, then you should enter:
319 It can happen that some of the tools have a suffix, when others
320 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
321 for that by checking the tools without the suffix in case it can
322 not find some of the tool.
324 endif # CROSS_NATIVE || CANADIAN