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 config TOOLCHAIN_PKGVERSION
71 prompt "Toolchain ID string"
72 default "crosstool-NG-${CT_VERSION}"
74 Specify a string that identifies your package. You may wish to include
75 a build number or build date. This version string will be included in
76 the output of gcc --version, and also in binutils, eglibc, gdb and
79 This is passed to the configure flag --with-pkgversion.
81 config TOOLCHAIN_BUGURL
83 prompt "Toolchain bug URL"
86 Specify the URL that users should visit if they wish to report a bug.
88 comment "Tuple completion and aliasing"
92 prompt "Tuple's vendor string"
95 Vendor part of the target tuple.
97 A tuple is of the form arch-vendor-kernel-system.
98 You can set the second part, vendor, to whatever you see fit.
99 Use a single word, or use underscores "_" to separate words.
100 Use neither dash nor space, as it breaks things.
102 Keep the default (unknown) if you don't know better.
104 config TARGET_ALIAS_SED_EXPR
106 prompt "Tuple's sed transform"
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 here a sed expression to be applied to ${CT_TARGET} to
114 create an alias for your toolchain.
116 For example, "s/${CT_TARGET_VENDOR}/foobar/" (without the double quotes)
117 will create the armeb-foobar-linux-uclibc alias to the above-mentioned
120 You shouldn't need to enter anything here, unless you plan to manually
121 call the tools (autotools-based ./configure will use the standard name).
125 prompt "Tuple's alias"
128 Normaly, you'd call your toolchain components (especially gcc) by
129 prefixing the target tuple followed by a dash and the component name
130 (eg. armeb-unknown-linux-uclibc-gcc).
132 You can enter a shortcut here. This string will be used to create
133 symbolic links to the toolchain tools (eg. if you enter "foo-bar" here,
134 then gcc for your toolchain will also be available as "foo-bar-gcc" along
135 with the original name).
137 You shouldn't need to enter anything here, unless you plan to manually
138 call the tools (autotools-based ./configure will use the standard name).
140 comment "Toolchain type"
149 prompt "Native (NO CODE!) (EXPERIMENTAL)"
150 depends on EXPERIMENTAL
152 Build a native toolchain.
153 See: "docs/6 - Toolchain types.txt"
159 Build a cross-toolchain.
160 See: "docs/6 - Toolchain types.txt"
164 prompt "Cross-native (NO CODE!) (EXPERIMENTAL)"
165 depends on EXPERIMENTAL
167 Build a cross-native toolchain.
168 See: "docs/6 - Toolchain types.txt"
172 prompt "Canadian (EXPERIMENTAL)"
173 depends on EXPERIMENTAL
175 Build a canadian-toolchain.
176 See: "docs/6 - Toolchain types.txt"
180 config TOOLCHAIN_TYPE
182 default "native" if NATIVE
183 default "cross" if CROSS
184 default "cross-native" if CROSS_NATIVE
185 default "canadian" if CANADIAN
187 comment "Build system"
191 prompt "| Tuple (READ HELP!)"
194 Canonical name of the machine building the toolchain.
195 You should leave empty, unless you really now what you're doing.
199 prompt "| Tools prefix (READ HELP!)"
202 If you have your *build system* tools in a weird location, and/or
203 they have an unusual prefix, enter it here.
205 Usually, you should leave that empty!
208 If your *build* gcc is /opt/build-tools/bin/weird-gcc then you
210 /opt/build-tools/bin/weird-
212 If your *build* gcc is /opt/build-tools/bin/weird-gcc and
213 /opt/build-tools/bin is in your PATH, you should enter:
216 If your *build* gcc is /opt/build-tools/bin/gcc then you
217 should enter (do not forget to add the trailing '/'):
218 /opt/build-tools/bin/
222 prompt "| Tools suffix (READ HELP!)"
225 If your *build system* tools have an unusual suffix, enter it
228 Usually, you should leave that empty!
231 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
232 installed as gcc-3.4, then you should enter:
235 It can happen that some of the tools have a suffix, when others
236 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
237 for that by checking the tools without the suffix in case it can
238 not find some of the tool.
242 comment "Host system"
246 prompt "| Tuple (READ HELP!)"
249 Canonical name of the machine running the toolchain.
253 prompt "| Tools prefix (READ HELP!)"
256 If you have your *host system* tools in a weird location, and/or
257 they have an unusual prefix, enter it here.
259 Usually, you should leave that empty!
262 If your *host* gcc is /opt/host-tools/bin/weird-gcc then you
264 /opt/host-tools/bin/weird-
266 If your *host* gcc is /opt/host-tools/bin/weird-gcc and
267 /opt/host-tools/bin is in your PATH, you should enter:
270 If your *host* gcc is /opt/host-tools/bin/gcc then you
271 should enter (do not forget to add the trailing '/'):
276 prompt "| Tools suffix (READ HELP!)"
279 If your *host system* tools have an unusual suffix, enter it
282 Usually, you should leave that empty!
285 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
286 installed as gcc-3.4, then you should enter:
289 It can happen that some of the tools have a suffix, when others
290 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
291 for that by checking the tools without the suffix in case it can
292 not find some of the tool.
296 if CROSS_NATIVE || CANADIAN
298 comment "Target system"
302 prompt "| Tools prefix (READ HELP!)"
305 If you have your *target system* tools in a weird location, and/or
306 they have an unusual prefix, enter it here.
308 Usually, you should leave that empty!
311 If your *target* gcc is /opt/target-tools/bin/weird-gcc then you
313 /opt/target-tools/bin/weird-
315 If your *target* gcc is /opt/target-tools/bin/weird-gcc and
316 /opt/target-tools/bin is in your PATH, you should enter:
319 If your *target* gcc is /opt/target-tools/bin/gcc then you
320 should enter (do not forget to add the trailing '/'):
321 /opt/target-tools/bin/
325 prompt "| Tools suffix (READ HELP!)"
328 If your *target system* tools have an unusual suffix, enter it
331 Usually, you should leave that empty!
334 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
335 installed as gcc-3.4, then you should enter:
338 It can happen that some of the tools have a suffix, when others
339 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
340 for that by checking the tools without the suffix in case it can
341 not find some of the tool.
343 endif # CROSS_NATIVE || CANADIAN