1.1 --- a/config/toolchain.in Sun Sep 14 16:21:07 2008 +0000
1.2 +++ b/config/toolchain.in Sun Jan 31 13:04:34 2010 +0100
1.3 @@ -81,7 +81,7 @@
1.4
1.5 config NATIVE
1.6 bool
1.7 - prompt "Native (EXPERIMENTAL)"
1.8 + prompt "Native (NO CODE!) (EXPERIMENTAL)"
1.9 depends on EXPERIMENTAL
1.10 help
1.11 Build a native toolchain.
1.12 @@ -96,7 +96,7 @@
1.13
1.14 config CROSS_NATIVE
1.15 bool
1.16 - prompt "Cross-native (EXPERIMENTAL)"
1.17 + prompt "Cross-native (NO CODE!) (EXPERIMENTAL)"
1.18 depends on EXPERIMENTAL
1.19 help
1.20 Build a cross-native toolchain.
1.21 @@ -104,7 +104,7 @@
1.22
1.23 config CANADIAN
1.24 bool
1.25 - prompt "Canadian (EXPERIMENTAL)"
1.26 + prompt "Canadian (NO CODE!) (EXPERIMENTAL)"
1.27 depends on EXPERIMENTAL
1.28 help
1.29 Build a canadian-toolchain.
1.30 @@ -119,48 +119,162 @@
1.31 default "cross-native" if CROSS_NATIVE
1.32 default "canadian" if CANADIAN
1.33
1.34 +comment "Build system"
1.35 +
1.36 config BUILD
1.37 string
1.38 - prompt "Build system tuple"
1.39 + prompt "| Tuple (READ HELP!)"
1.40 default ""
1.41 help
1.42 Canonical name of the machine building the toolchain.
1.43 You should leave empty, unless you really now what you're doing.
1.44
1.45 -config CC_NATIVE
1.46 +config BUILD_PREFIX
1.47 string
1.48 - prompt "Native gcc"
1.49 - default "gcc"
1.50 + prompt "| Tools prefix (READ HELP!)"
1.51 + default ""
1.52 help
1.53 - The native C compiler.
1.54 + If you have your *build system* tools in a weird location, and/or
1.55 + they have an unusual prefix, enter it here.
1.56
1.57 - You can set this to an alternative compiler if you have more than one
1.58 - installed (eg. gcc is gcc-4.1.1 and you want to use gcc-3.4.6).
1.59 + Usually, you should leave that empty!
1.60
1.61 - You can leave this empty as well, in which case gcc will be used.
1.62 + Eg.:
1.63 + If your *build* gcc is /opt/build-tools/bin/weird-gcc then you
1.64 + should enter:
1.65 + /opt/build-tools/bin/weird-
1.66 +
1.67 + If your *build* gcc is /opt/build-tools/bin/weird-gcc and
1.68 + /opt/build-tools/bin is in your PATH, you should enter:
1.69 + weird-
1.70 +
1.71 + If your *build* gcc is /opt/build-tools/bin/gcc then you
1.72 + should enter (do not forget to add the trailing '/'):
1.73 + /opt/build-tools/bin/
1.74 +
1.75 +config BUILD_SUFFIX
1.76 + string
1.77 + prompt "| Tools suffix (READ HELP!)"
1.78 + default ""
1.79 + help
1.80 + If your *build system* tools have an unusual suffix, enter it
1.81 + here.
1.82 +
1.83 + Usually, you should leave that empty!
1.84 +
1.85 + Eg.:
1.86 + If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
1.87 + installed as gcc-3.4, then you should enter:
1.88 + -3.4
1.89 +
1.90 + It can happen that some of the tools have a suffix, when others
1.91 + don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
1.92 + for that by checking the tools without the suffix in case it can
1.93 + not find some of the tool.
1.94 +
1.95 +if CANADIAN
1.96 +
1.97 +comment "Host system"
1.98
1.99 config HOST
1.100 string
1.101 - prompt "Host system tuple"
1.102 + prompt "| Tuple (READ HELP!)"
1.103 default ""
1.104 - depends on NATIVE || CANADIAN
1.105 help
1.106 Canonical name of the machine running the toolchain.
1.107
1.108 -config HOST_CC
1.109 +config HOST_PREFIX
1.110 string
1.111 - prompt "Cross-compiler prefix for host system"
1.112 - default "${CT_HOST}-"
1.113 - depends on NATIVE || CANADIAN
1.114 + prompt "| Tools prefix (READ HELP!)"
1.115 + default ""
1.116 help
1.117 - C compiler targeting the host system.
1.118 + If you have your *host system* tools in a weird location, and/or
1.119 + they have an unusual prefix, enter it here.
1.120 +
1.121 + Usually, you should leave that empty!
1.122 +
1.123 + Eg.:
1.124 + If your *host* gcc is /opt/host-tools/bin/weird-gcc then you
1.125 + should enter:
1.126 + /opt/host-tools/bin/weird-
1.127 +
1.128 + If your *host* gcc is /opt/host-tools/bin/weird-gcc and
1.129 + /opt/host-tools/bin is in your PATH, you should enter:
1.130 + weird-
1.131 +
1.132 + If your *host* gcc is /opt/host-tools/bin/gcc then you
1.133 + should enter (do not forget to add the trailing '/'):
1.134 + /opt/host-tools/bin/
1.135
1.136 -config TARGET_CC
1.137 +config HOST_SUFFIX
1.138 string
1.139 - prompt "Cross-compiler prefix for target system"
1.140 - default "${CT_TARGET}-"
1.141 - depends on CANADIAN
1.142 + prompt "| Tools suffix (READ HELP!)"
1.143 + default ""
1.144 help
1.145 - C compiler targeting the target system.
1.146 + If your *host system* tools have an unusual suffix, enter it
1.147 + here.
1.148 +
1.149 + Usually, you should leave that empty!
1.150 +
1.151 + Eg.:
1.152 + If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
1.153 + installed as gcc-3.4, then you should enter:
1.154 + -3.4
1.155 +
1.156 + It can happen that some of the tools have a suffix, when others
1.157 + don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
1.158 + for that by checking the tools without the suffix in case it can
1.159 + not find some of the tool.
1.160 +
1.161 +endif # CANADIAN
1.162 +
1.163 +if CROSS_NATIVE || CANADIAN
1.164 +
1.165 +comment "Target system"
1.166 +
1.167 +config TARGET_PREFIX
1.168 + string
1.169 + prompt "| Tools prefix (READ HELP!)"
1.170 + default ""
1.171 + help
1.172 + If you have your *target system* tools in a weird location, and/or
1.173 + they have an unusual prefix, enter it here.
1.174 +
1.175 + Usually, you should leave that empty!
1.176 +
1.177 + Eg.:
1.178 + If your *target* gcc is /opt/target-tools/bin/weird-gcc then you
1.179 + should enter:
1.180 + /opt/target-tools/bin/weird-
1.181 +
1.182 + If your *target* gcc is /opt/target-tools/bin/weird-gcc and
1.183 + /opt/target-tools/bin is in your PATH, you should enter:
1.184 + weird-
1.185 +
1.186 + If your *target* gcc is /opt/target-tools/bin/gcc then you
1.187 + should enter (do not forget to add the trailing '/'):
1.188 + /opt/target-tools/bin/
1.189 +
1.190 +config TARGET_SUFFIX
1.191 + string
1.192 + prompt "| Tools suffix (READ HELP!)"
1.193 + default ""
1.194 + help
1.195 + If your *target system* tools have an unusual suffix, enter it
1.196 + here.
1.197 +
1.198 + Usually, you should leave that empty!
1.199 +
1.200 + Eg.:
1.201 + If your 'default' gcc is gcc 4.3.1, but you also have gcc-3.4.2
1.202 + installed as gcc-3.4, then you should enter:
1.203 + -3.4
1.204 +
1.205 + It can happen that some of the tools have a suffix, when others
1.206 + don't, eg. you can have 'gcc-3.4' and 'ar'. crosstool-NG accounts
1.207 + for that by checking the tools without the suffix in case it can
1.208 + not find some of the tool.
1.209 +
1.210 +endif # CROSS_NATIVE || CANADIAN
1.211
1.212 endmenu