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.
36 Use neither dash nor space, as it breaks things.
38 Keep the default (unkown) if you don't know better.
40 config TARGET_ALIAS_SED_EXPR
42 prompt "Target sed transform"
45 Normaly, you'd call your toolchain components (especially gcc) by
46 prefixing the target tuple followed by a dash and the component name
47 (eg. armeb-unknown-linux-uclibc-gcc).
49 You can enter here a sed expression to be applied to ${CT_TARGET} to
50 create an alias for your toolchain.
52 For example, "s/${CT_TARGET_VENDOR}/foobar/" (without the double quotes)
53 will create the armeb-foobar-linux-uclibc alias to the above-mentioned
56 You shouldn't need to enter anything here, unless you plan to manually
57 call the tools (autotools-based ./configure will use the standard name).
64 Normaly, you'd call your toolchain components (especially gcc) by
65 prefixing the target tuple followed by a dash and the component name
66 (eg. armeb-unknown-linux-uclibc-gcc).
68 You can enter a shortcut here. This string will be used to create
69 symbolic links to the toolchain tools (eg. if you enter "foo-bar" here,
70 then gcc for your toolchain will also be available as "foo-bar-gcc" along
71 with the original name).
73 You shouldn't need to enter anything here, unless you plan to manually
74 call the tools (autotools-based ./configure will use the standard name).
76 comment "Toolchain type"
85 prompt "Native (NO CODE!) (EXPERIMENTAL)"
86 depends on EXPERIMENTAL
88 Build a native toolchain.
95 Build a cross-toolchain.
100 prompt "Cross-native (NO CODE!) (EXPERIMENTAL)"
101 depends on EXPERIMENTAL
103 Build a cross-native toolchain.
104 See docs/overview.txt
108 prompt "Canadian (NO CODE!) (EXPERIMENTAL)"
109 depends on EXPERIMENTAL
111 Build a canadian-toolchain.
112 See docs/overview.txt
116 config TOOLCHAIN_TYPE
118 default "native" if NATIVE
119 default "cross" if CROSS
120 default "cross-native" if CROSS_NATIVE
121 default "canadian" if CANADIAN
123 comment "Build system"
127 prompt "| Tuple (READ HELP!)"
130 Canonical name of the machine building the toolchain.
131 You should leave empty, unless you really now what you're doing.
135 prompt "| Tools prefix (READ HELP!)"
138 If you have your *build system* tools in a weird location, and/or
139 they have an unusual prefix, enter it here.
141 Usually, you should leave that empty!
144 If your *build* gcc is /opt/build-tools/bin/weird-gcc then you
146 /opt/build-tools/bin/weird-
148 If your *build* gcc is /opt/build-tools/bin/weird-gcc and
149 /opt/build-tools/bin is in your PATH, you should enter:
152 If your *build* gcc is /opt/build-tools/bin/gcc then you
153 should enter (do not forget to add the trailing '/'):
154 /opt/build-tools/bin/
158 prompt "| Tools suffix (READ HELP!)"
161 If your *build system* tools have an unusual suffix, enter it
164 Usually, you should leave that empty!
167 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
168 installed as gcc-3.4, then you should enter:
171 It can happen that some of the tools have a suffix, when others
172 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
173 for that by checking the tools without the suffix in case it can
174 not find some of the tool.
178 comment "Host system"
182 prompt "| Tuple (READ HELP!)"
185 Canonical name of the machine running the toolchain.
189 prompt "| Tools prefix (READ HELP!)"
192 If you have your *host system* tools in a weird location, and/or
193 they have an unusual prefix, enter it here.
195 Usually, you should leave that empty!
198 If your *host* gcc is /opt/host-tools/bin/weird-gcc then you
200 /opt/host-tools/bin/weird-
202 If your *host* gcc is /opt/host-tools/bin/weird-gcc and
203 /opt/host-tools/bin is in your PATH, you should enter:
206 If your *host* gcc is /opt/host-tools/bin/gcc then you
207 should enter (do not forget to add the trailing '/'):
212 prompt "| Tools suffix (READ HELP!)"
215 If your *host system* tools have an unusual suffix, enter it
218 Usually, you should leave that empty!
221 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
222 installed as gcc-3.4, then you should enter:
225 It can happen that some of the tools have a suffix, when others
226 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
227 for that by checking the tools without the suffix in case it can
228 not find some of the tool.
232 if CROSS_NATIVE || CANADIAN
234 comment "Target system"
238 prompt "| Tools prefix (READ HELP!)"
241 If you have your *target system* tools in a weird location, and/or
242 they have an unusual prefix, enter it here.
244 Usually, you should leave that empty!
247 If your *target* gcc is /opt/target-tools/bin/weird-gcc then you
249 /opt/target-tools/bin/weird-
251 If your *target* gcc is /opt/target-tools/bin/weird-gcc and
252 /opt/target-tools/bin is in your PATH, you should enter:
255 If your *target* gcc is /opt/target-tools/bin/gcc then you
256 should enter (do not forget to add the trailing '/'):
257 /opt/target-tools/bin/
261 prompt "| Tools suffix (READ HELP!)"
264 If your *target system* tools have an unusual suffix, enter it
267 Usually, you should leave that empty!
270 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
271 installed as gcc-3.4, then you should enter:
274 It can happen that some of the tools have a suffix, when others
275 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
276 for that by checking the tools without the suffix in case it can
277 not find some of the tool.
279 endif # CROSS_NATIVE || CANADIAN