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.
78 This is passed to the configure flag --with-pkgversion.
80 config TOOLCHAIN_BUGURL
82 prompt "Toolchain bug URL"
85 Specify the URL that users should visit if they wish to report a bug.
87 comment "Tuple completion and aliasing"
91 prompt "Tuple's vendor string"
94 Vendor part of the target tuple.
96 A tuple is of the form arch-vendor-kernel-system.
97 You can set the second part, vendor, to whatever you see fit.
98 Use a single word, or use underscores "_" to separate words.
99 Use neither dash nor space, as it breaks things.
101 Keep the default (unknown) if you don't know better.
103 config TARGET_ALIAS_SED_EXPR
105 prompt "Tuple's sed transform"
108 Normaly, you'd call your toolchain components (especially gcc) by
109 prefixing the target tuple followed by a dash and the component name
110 (eg. armeb-unknown-linux-uclibc-gcc).
112 You can enter here a sed expression to be applied to ${CT_TARGET} to
113 create an alias for your toolchain.
115 For example, "s/${CT_TARGET_VENDOR}/foobar/" (without the double quotes)
116 will create the armeb-foobar-linux-uclibc alias to the above-mentioned
119 You shouldn't need to enter anything here, unless you plan to manually
120 call the tools (autotools-based ./configure will use the standard name).
124 prompt "Tuple's alias"
127 Normaly, you'd call your toolchain components (especially gcc) by
128 prefixing the target tuple followed by a dash and the component name
129 (eg. armeb-unknown-linux-uclibc-gcc).
131 You can enter a shortcut here. This string will be used to create
132 symbolic links to the toolchain tools (eg. if you enter "foo-bar" here,
133 then gcc for your toolchain will also be available as "foo-bar-gcc" along
134 with the original name).
136 You shouldn't need to enter anything here, unless you plan to manually
137 call the tools (autotools-based ./configure will use the standard name).
139 comment "Toolchain type"
148 prompt "Native (NO CODE!) (EXPERIMENTAL)"
149 depends on EXPERIMENTAL
151 Build a native toolchain.
152 See: "docs/6 - Toolchain types.txt"
158 Build a cross-toolchain.
159 See: "docs/6 - Toolchain types.txt"
163 prompt "Cross-native (NO CODE!) (EXPERIMENTAL)"
164 depends on EXPERIMENTAL
166 Build a cross-native toolchain.
167 See: "docs/6 - Toolchain types.txt"
171 prompt "Canadian (EXPERIMENTAL)"
172 depends on EXPERIMENTAL
174 Build a canadian-toolchain.
175 See: "docs/6 - Toolchain types.txt"
179 config TOOLCHAIN_TYPE
181 default "native" if NATIVE
182 default "cross" if CROSS
183 default "cross-native" if CROSS_NATIVE
184 default "canadian" if CANADIAN
186 comment "Build system"
190 prompt "| Tuple (READ HELP!)"
193 Canonical name of the machine building the toolchain.
194 You should leave empty, unless you really now what you're doing.
198 prompt "| Tools prefix (READ HELP!)"
201 If you have your *build system* tools in a weird location, and/or
202 they have an unusual prefix, enter it here.
204 Usually, you should leave that empty!
207 If your *build* gcc is /opt/build-tools/bin/weird-gcc then you
209 /opt/build-tools/bin/weird-
211 If your *build* gcc is /opt/build-tools/bin/weird-gcc and
212 /opt/build-tools/bin is in your PATH, you should enter:
215 If your *build* gcc is /opt/build-tools/bin/gcc then you
216 should enter (do not forget to add the trailing '/'):
217 /opt/build-tools/bin/
221 prompt "| Tools suffix (READ HELP!)"
224 If your *build system* tools have an unusual suffix, enter it
227 Usually, you should leave that empty!
230 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
231 installed as gcc-3.4, then you should enter:
234 It can happen that some of the tools have a suffix, when others
235 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
236 for that by checking the tools without the suffix in case it can
237 not find some of the tool.
241 comment "Host system"
245 prompt "| Tuple (READ HELP!)"
248 Canonical name of the machine running the toolchain.
252 prompt "| Tools prefix (READ HELP!)"
255 If you have your *host system* tools in a weird location, and/or
256 they have an unusual prefix, enter it here.
258 Usually, you should leave that empty!
261 If your *host* gcc is /opt/host-tools/bin/weird-gcc then you
263 /opt/host-tools/bin/weird-
265 If your *host* gcc is /opt/host-tools/bin/weird-gcc and
266 /opt/host-tools/bin is in your PATH, you should enter:
269 If your *host* gcc is /opt/host-tools/bin/gcc then you
270 should enter (do not forget to add the trailing '/'):
275 prompt "| Tools suffix (READ HELP!)"
278 If your *host system* tools have an unusual suffix, enter it
281 Usually, you should leave that empty!
284 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
285 installed as gcc-3.4, then you should enter:
288 It can happen that some of the tools have a suffix, when others
289 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
290 for that by checking the tools without the suffix in case it can
291 not find some of the tool.
295 if CROSS_NATIVE || CANADIAN
297 comment "Target system"
301 prompt "| Tools prefix (READ HELP!)"
304 If you have your *target system* tools in a weird location, and/or
305 they have an unusual prefix, enter it here.
307 Usually, you should leave that empty!
310 If your *target* gcc is /opt/target-tools/bin/weird-gcc then you
312 /opt/target-tools/bin/weird-
314 If your *target* gcc is /opt/target-tools/bin/weird-gcc and
315 /opt/target-tools/bin is in your PATH, you should enter:
318 If your *target* gcc is /opt/target-tools/bin/gcc then you
319 should enter (do not forget to add the trailing '/'):
320 /opt/target-tools/bin/
324 prompt "| Tools suffix (READ HELP!)"
327 If your *target system* tools have an unusual suffix, enter it
330 Usually, you should leave that empty!
333 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
334 installed as gcc-3.4, then you should enter:
337 It can happen that some of the tools have a suffix, when others
338 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
339 for that by checking the tools without the suffix in case it can
340 not find some of the tool.
342 endif # CROSS_NATIVE || CANADIAN