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'.
15 config SYSROOT_DIR_PREFIX
17 prompt "sysroot prefix dir (READ HELP)" if ! BACKEND
18 depends on USE_SYSROOT
22 * Unless you realy know you need that, leave it empty!
25 This string will be interpreted as a directory component to be added
26 to the sysroot path, just before the actual sysroot directory.
28 In fact, the sysroot path is constructed as:
29 ${CT_PREFIX_DIR}/${CT_TARGET}/${CT_SYSROOT_DIR_PREFIX}/sys-root
31 config STATIC_TOOLCHAIN
33 prompt "Build Static Toolchain (EXPERIMENTAL)"
34 depends on EXPERIMENTAL
37 Build static host binaries.
39 If you wish to move the toolchain to another host, and you are not
40 confident that this host has the required versions of system libs, then
41 you can say 'Y' here, and all the host tools will be linked staticaly.
43 The impacted tools are:
46 The default is 'N', to build dynamicaly-linked host binaries.
48 NOTE: this has no connection to whether the target libraries will be
49 dynamic or static. This only applies to the tools themselves.
51 comment "Tuple completion and aliasing"
55 prompt "Tuple's vendor string"
58 Vendor part of the target tuple.
60 A tuple is of the form arch-vendor-kernel-system.
61 You can set the second part, vendor, to whatever you see fit.
62 Use a single word, or use underscores "_" to separate words.
63 Use neither dash nor space, as it breaks things.
65 Keep the default (unknown) if you don't know better.
67 config TARGET_ALIAS_SED_EXPR
69 prompt "Tuple's sed transform"
72 Normaly, you'd call your toolchain components (especially gcc) by
73 prefixing the target tuple followed by a dash and the component name
74 (eg. armeb-unknown-linux-uclibc-gcc).
76 You can enter here a sed expression to be applied to ${CT_TARGET} to
77 create an alias for your toolchain.
79 For example, "s/${CT_TARGET_VENDOR}/foobar/" (without the double quotes)
80 will create the armeb-foobar-linux-uclibc alias to the above-mentioned
83 You shouldn't need to enter anything here, unless you plan to manually
84 call the tools (autotools-based ./configure will use the standard name).
88 prompt "Tuple's alias"
91 Normaly, you'd call your toolchain components (especially gcc) by
92 prefixing the target tuple followed by a dash and the component name
93 (eg. armeb-unknown-linux-uclibc-gcc).
95 You can enter a shortcut here. This string will be used to create
96 symbolic links to the toolchain tools (eg. if you enter "foo-bar" here,
97 then gcc for your toolchain will also be available as "foo-bar-gcc" along
98 with the original name).
100 You shouldn't need to enter anything here, unless you plan to manually
101 call the tools (autotools-based ./configure will use the standard name).
103 comment "Toolchain type"
112 prompt "Native (NO CODE!) (EXPERIMENTAL)"
113 depends on EXPERIMENTAL
115 Build a native toolchain.
116 See docs/overview.txt
122 Build a cross-toolchain.
123 See docs/overview.txt
127 prompt "Cross-native (NO CODE!) (EXPERIMENTAL)"
128 depends on EXPERIMENTAL
130 Build a cross-native toolchain.
131 See docs/overview.txt
135 prompt "Canadian (EXPERIMENTAL)"
136 depends on EXPERIMENTAL
138 Build a canadian-toolchain.
139 See docs/overview.txt
143 config TOOLCHAIN_TYPE
145 default "native" if NATIVE
146 default "cross" if CROSS
147 default "cross-native" if CROSS_NATIVE
148 default "canadian" if CANADIAN
150 comment "Build system"
154 prompt "| Tuple (READ HELP!)"
157 Canonical name of the machine building the toolchain.
158 You should leave empty, unless you really now what you're doing.
162 prompt "| Tools prefix (READ HELP!)"
165 If you have your *build system* tools in a weird location, and/or
166 they have an unusual prefix, enter it here.
168 Usually, you should leave that empty!
171 If your *build* gcc is /opt/build-tools/bin/weird-gcc then you
173 /opt/build-tools/bin/weird-
175 If your *build* gcc is /opt/build-tools/bin/weird-gcc and
176 /opt/build-tools/bin is in your PATH, you should enter:
179 If your *build* gcc is /opt/build-tools/bin/gcc then you
180 should enter (do not forget to add the trailing '/'):
181 /opt/build-tools/bin/
185 prompt "| Tools suffix (READ HELP!)"
188 If your *build system* tools have an unusual suffix, enter it
191 Usually, you should leave that empty!
194 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
195 installed as gcc-3.4, then you should enter:
198 It can happen that some of the tools have a suffix, when others
199 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
200 for that by checking the tools without the suffix in case it can
201 not find some of the tool.
205 comment "Host system"
209 prompt "| Tuple (READ HELP!)"
212 Canonical name of the machine running the toolchain.
216 prompt "| Tools prefix (READ HELP!)"
219 If you have your *host system* tools in a weird location, and/or
220 they have an unusual prefix, enter it here.
222 Usually, you should leave that empty!
225 If your *host* gcc is /opt/host-tools/bin/weird-gcc then you
227 /opt/host-tools/bin/weird-
229 If your *host* gcc is /opt/host-tools/bin/weird-gcc and
230 /opt/host-tools/bin is in your PATH, you should enter:
233 If your *host* gcc is /opt/host-tools/bin/gcc then you
234 should enter (do not forget to add the trailing '/'):
239 prompt "| Tools suffix (READ HELP!)"
242 If your *host system* tools have an unusual suffix, enter it
245 Usually, you should leave that empty!
248 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
249 installed as gcc-3.4, then you should enter:
252 It can happen that some of the tools have a suffix, when others
253 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
254 for that by checking the tools without the suffix in case it can
255 not find some of the tool.
259 if CROSS_NATIVE || CANADIAN
261 comment "Target system"
265 prompt "| Tools prefix (READ HELP!)"
268 If you have your *target system* tools in a weird location, and/or
269 they have an unusual prefix, enter it here.
271 Usually, you should leave that empty!
274 If your *target* gcc is /opt/target-tools/bin/weird-gcc then you
276 /opt/target-tools/bin/weird-
278 If your *target* gcc is /opt/target-tools/bin/weird-gcc and
279 /opt/target-tools/bin is in your PATH, you should enter:
282 If your *target* gcc is /opt/target-tools/bin/gcc then you
283 should enter (do not forget to add the trailing '/'):
284 /opt/target-tools/bin/
288 prompt "| Tools suffix (READ HELP!)"
291 If your *target system* tools have an unusual suffix, enter it
294 Usually, you should leave that empty!
297 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
298 installed as gcc-3.4, then you should enter:
301 It can happen that some of the tools have a suffix, when others
302 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
303 for that by checking the tools without the suffix in case it can
304 not find some of the tool.
306 endif # CROSS_NATIVE || CANADIAN