Some eye-candy in the toolchain sub-menu entries.
/trunk/config/toolchain.in | 8 5 3 0 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
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
19 depends on EXPERIMENTAL
23 * Unless you realy know you need that, leave it empty!
26 This string will be interpreted as a directory component to be added
27 to the sysroot path, just before the actual sysroot directory.
29 In fact, the sysroot path is constructed as:
30 ${CT_PREFIX_DIR}/${CT_TARGET}/${CT_SYSROOT_DIR_PREFIX}/sys-root
34 prompt "Build shared libraries"
35 depends on ! BARE_METAL
38 Say 'y' here, unless you don't want shared libraries.
40 You might not want shared libraries if you're building for a target that
41 don't support it (maybe some nommu targets, for example, or bare metal).
43 comment "Tuple completion and aliasing"
47 prompt "Tuple's vendor string"
50 Vendor part of the target tuple.
52 A tuple is of the form arch-vendor-kernel-system.
53 You can set the second part, vendor, to whatever you see fit.
54 Use a single word, or use underscores "_" to separate words.
55 Use neither dash nor space, as it breaks things.
57 Keep the default (unkown) if you don't know better.
59 config TARGET_ALIAS_SED_EXPR
61 prompt "Tuple's sed transform"
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 here a sed expression to be applied to ${CT_TARGET} to
69 create an alias for your toolchain.
71 For example, "s/${CT_TARGET_VENDOR}/foobar/" (without the double quotes)
72 will create the armeb-foobar-linux-uclibc alias to the above-mentioned
75 You shouldn't need to enter anything here, unless you plan to manually
76 call the tools (autotools-based ./configure will use the standard name).
80 prompt "Tuple's alias"
83 Normaly, you'd call your toolchain components (especially gcc) by
84 prefixing the target tuple followed by a dash and the component name
85 (eg. armeb-unknown-linux-uclibc-gcc).
87 You can enter a shortcut here. This string will be used to create
88 symbolic links to the toolchain tools (eg. if you enter "foo-bar" here,
89 then gcc for your toolchain will also be available as "foo-bar-gcc" along
90 with the original name).
92 You shouldn't need to enter anything here, unless you plan to manually
93 call the tools (autotools-based ./configure will use the standard name).
95 comment "Toolchain type"
104 prompt "Native (NO CODE!) (EXPERIMENTAL)"
105 depends on EXPERIMENTAL
107 Build a native toolchain.
108 See docs/overview.txt
114 Build a cross-toolchain.
115 See docs/overview.txt
119 prompt "Cross-native (NO CODE!) (EXPERIMENTAL)"
120 depends on EXPERIMENTAL
122 Build a cross-native toolchain.
123 See docs/overview.txt
127 prompt "Canadian (NO CODE!) (EXPERIMENTAL)"
128 depends on EXPERIMENTAL
130 Build a canadian-toolchain.
131 See docs/overview.txt
135 config TOOLCHAIN_TYPE
137 default "native" if NATIVE
138 default "cross" if CROSS
139 default "cross-native" if CROSS_NATIVE
140 default "canadian" if CANADIAN
142 comment "Build system"
146 prompt "| Tuple (READ HELP!)"
149 Canonical name of the machine building the toolchain.
150 You should leave empty, unless you really now what you're doing.
154 prompt "| Tools prefix (READ HELP!)"
157 If you have your *build system* tools in a weird location, and/or
158 they have an unusual prefix, enter it here.
160 Usually, you should leave that empty!
163 If your *build* gcc is /opt/build-tools/bin/weird-gcc then you
165 /opt/build-tools/bin/weird-
167 If your *build* gcc is /opt/build-tools/bin/weird-gcc and
168 /opt/build-tools/bin is in your PATH, you should enter:
171 If your *build* gcc is /opt/build-tools/bin/gcc then you
172 should enter (do not forget to add the trailing '/'):
173 /opt/build-tools/bin/
177 prompt "| Tools suffix (READ HELP!)"
180 If your *build system* tools have an unusual suffix, enter it
183 Usually, you should leave that empty!
186 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
187 installed as gcc-3.4, then you should enter:
190 It can happen that some of the tools have a suffix, when others
191 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
192 for that by checking the tools without the suffix in case it can
193 not find some of the tool.
197 comment "Host system"
201 prompt "| Tuple (READ HELP!)"
204 Canonical name of the machine running the toolchain.
208 prompt "| Tools prefix (READ HELP!)"
211 If you have your *host system* tools in a weird location, and/or
212 they have an unusual prefix, enter it here.
214 Usually, you should leave that empty!
217 If your *host* gcc is /opt/host-tools/bin/weird-gcc then you
219 /opt/host-tools/bin/weird-
221 If your *host* gcc is /opt/host-tools/bin/weird-gcc and
222 /opt/host-tools/bin is in your PATH, you should enter:
225 If your *host* gcc is /opt/host-tools/bin/gcc then you
226 should enter (do not forget to add the trailing '/'):
231 prompt "| Tools suffix (READ HELP!)"
234 If your *host system* tools have an unusual suffix, enter it
237 Usually, you should leave that empty!
240 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
241 installed as gcc-3.4, then you should enter:
244 It can happen that some of the tools have a suffix, when others
245 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
246 for that by checking the tools without the suffix in case it can
247 not find some of the tool.
251 if CROSS_NATIVE || CANADIAN
253 comment "Target system"
257 prompt "| Tools prefix (READ HELP!)"
260 If you have your *target system* tools in a weird location, and/or
261 they have an unusual prefix, enter it here.
263 Usually, you should leave that empty!
266 If your *target* gcc is /opt/target-tools/bin/weird-gcc then you
268 /opt/target-tools/bin/weird-
270 If your *target* gcc is /opt/target-tools/bin/weird-gcc and
271 /opt/target-tools/bin is in your PATH, you should enter:
274 If your *target* gcc is /opt/target-tools/bin/gcc then you
275 should enter (do not forget to add the trailing '/'):
276 /opt/target-tools/bin/
280 prompt "| Tools suffix (READ HELP!)"
283 If your *target system* tools have an unusual suffix, enter it
286 Usually, you should leave that empty!
289 If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
290 installed as gcc-3.4, then you should enter:
293 It can happen that some of the tools have a suffix, when others
294 don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
295 for that by checking the tools without the suffix in case it can
296 not find some of the tool.
298 endif # CROSS_NATIVE || CANADIAN