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)"
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
33 prompt "Build shared libraries"
34 depends on ! BARE_METAL
37 Say 'y' here, unless you don't want shared libraries.
39 You might not want shared libraries if you're building for a target that
40 don't support it (maybe some nommu targets, for example, or bare metal).
42 comment "Tuple completion and aliasing"
46 prompt "Tuple's vendor string"
49 Vendor part of the target tuple.
51 A tuple is of the form arch-vendor-kernel-system.
52 You can set the second part, vendor, to whatever you see fit.
53 Use a single word, or use underscores "_" to separate words.
54 Use neither dash nor space, as it breaks things.
56 Keep the default (unkown) if you don't know better.
58 config TARGET_ALIAS_SED_EXPR
60 prompt "Tuple's sed transform"
63 Normaly, you'd call your toolchain components (especially gcc) by
64 prefixing the target tuple followed by a dash and the component name
65 (eg. armeb-unknown-linux-uclibc-gcc).
67 You can enter here a sed expression to be applied to ${CT_TARGET} to
68 create an alias for your toolchain.
70 For example, "s/${CT_TARGET_VENDOR}/foobar/" (without the double quotes)
71 will create the armeb-foobar-linux-uclibc alias to the above-mentioned
74 You shouldn't need to enter anything here, unless you plan to manually
75 call the tools (autotools-based ./configure will use the standard name).
79 prompt "Tuple's alias"
82 Normaly, you'd call your toolchain components (especially gcc) by
83 prefixing the target tuple followed by a dash and the component name
84 (eg. armeb-unknown-linux-uclibc-gcc).
86 You can enter a shortcut here. This string will be used to create
87 symbolic links to the toolchain tools (eg. if you enter "foo-bar" here,
88 then gcc for your toolchain will also be available as "foo-bar-gcc" along
89 with the original name).
91 You shouldn't need to enter anything here, unless you plan to manually
92 call the tools (autotools-based ./configure will use the standard name).
94 comment "Toolchain type"
103 prompt "Native (NO CODE!) (EXPERIMENTAL)"
104 depends on EXPERIMENTAL
106 Build a native toolchain.
107 See docs/overview.txt
113 Build a cross-toolchain.
114 See docs/overview.txt
118 prompt "Cross-native (NO CODE!) (EXPERIMENTAL)"
119 depends on EXPERIMENTAL
121 Build a cross-native toolchain.
122 See docs/overview.txt
126 prompt "Canadian (EXPERIMENTAL)"
127 depends on EXPERIMENTAL
129 Build a canadian-toolchain.
130 See docs/overview.txt
134 config TOOLCHAIN_TYPE
136 default "native" if NATIVE
137 default "cross" if CROSS
138 default "cross-native" if CROSS_NATIVE
139 default "canadian" if CANADIAN
141 comment "Build system"
145 prompt "| Tuple (READ HELP!)"
148 Canonical name of the machine building the toolchain.
149 You should leave empty, unless you really now what you're doing.
153 prompt "| Tools prefix (READ HELP!)"
156 If you have your *build system* tools in a weird location, and/or
157 they have an unusual prefix, enter it here.
159 Usually, you should leave that empty!
162 If your *build* gcc is /opt/build-tools/bin/weird-gcc then you
164 /opt/build-tools/bin/weird-
166 If your *build* gcc is /opt/build-tools/bin/weird-gcc and
167 /opt/build-tools/bin is in your PATH, you should enter:
170 If your *build* gcc is /opt/build-tools/bin/gcc then you
171 should enter (do not forget to add the trailing '/'):
172 /opt/build-tools/bin/
176 prompt "| Tools suffix (READ HELP!)"
179 If your *build system* tools have an unusual suffix, enter it
182 Usually, you should leave that empty!
185 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
186 installed as gcc-3.4, then you should enter:
189 It can happen that some of the tools have a suffix, when others
190 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
191 for that by checking the tools without the suffix in case it can
192 not find some of the tool.
196 comment "Host system"
200 prompt "| Tuple (READ HELP!)"
203 Canonical name of the machine running the toolchain.
207 prompt "| Tools prefix (READ HELP!)"
210 If you have your *host system* tools in a weird location, and/or
211 they have an unusual prefix, enter it here.
213 Usually, you should leave that empty!
216 If your *host* gcc is /opt/host-tools/bin/weird-gcc then you
218 /opt/host-tools/bin/weird-
220 If your *host* gcc is /opt/host-tools/bin/weird-gcc and
221 /opt/host-tools/bin is in your PATH, you should enter:
224 If your *host* gcc is /opt/host-tools/bin/gcc then you
225 should enter (do not forget to add the trailing '/'):
230 prompt "| Tools suffix (READ HELP!)"
233 If your *host system* tools have an unusual suffix, enter it
236 Usually, you should leave that empty!
239 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
240 installed as gcc-3.4, then you should enter:
243 It can happen that some of the tools have a suffix, when others
244 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
245 for that by checking the tools without the suffix in case it can
246 not find some of the tool.
250 if CROSS_NATIVE || CANADIAN
252 comment "Target system"
256 prompt "| Tools prefix (READ HELP!)"
259 If you have your *target system* tools in a weird location, and/or
260 they have an unusual prefix, enter it here.
262 Usually, you should leave that empty!
265 If your *target* gcc is /opt/target-tools/bin/weird-gcc then you
267 /opt/target-tools/bin/weird-
269 If your *target* gcc is /opt/target-tools/bin/weird-gcc and
270 /opt/target-tools/bin is in your PATH, you should enter:
273 If your *target* gcc is /opt/target-tools/bin/gcc then you
274 should enter (do not forget to add the trailing '/'):
275 /opt/target-tools/bin/
279 prompt "| Tools suffix (READ HELP!)"
282 If your *target system* tools have an unusual suffix, enter it
285 Usually, you should leave that empty!
288 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
289 installed as gcc-3.4, then you should enter:
292 It can happen that some of the tools have a suffix, when others
293 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
294 for that by checking the tools without the suffix in case it can
295 not find some of the tool.
297 endif # CROSS_NATIVE || CANADIAN