Break-down config/global.in into smaller, much more maintainable files.
config/paths.in | 419 1 418 0 --------------------------------------------------------
1 file changed, 1 insertion(+), 418 deletions(-)
1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/config/build-behave.in Thu Apr 17 20:02:07 2008 +0000
1.3 @@ -0,0 +1,45 @@
1.4 +# Options related to how the build behaves
1.5 +
1.6 +comment "Build behavior"
1.7 +
1.8 +config PARALLEL_JOBS
1.9 + int
1.10 + prompt "Number of parallel jobs"
1.11 + default 1
1.12 + help
1.13 + Number of jobs make will be allowed to run concurently.
1.14 + Set this higher than the number of processors you have, but not too high.
1.15 + A good rule of thumb is twice the number of processors you have.
1.16 +
1.17 + Enter 1 (or 0) to have only one job at a time.
1.18 +
1.19 +config LOAD
1.20 + int
1.21 + prompt "Maximum allowed load"
1.22 + default 0
1.23 + help
1.24 + Specifies that no new jobs should be started if there are others jobs
1.25 + running and the load average is at least this value.
1.26 +
1.27 + Makes sense on SMP machines only.
1.28 +
1.29 + Enter 0 to have no limit on the load average.
1.30 +
1.31 + Note: only the integer part of the load is allowed here (you can't enter
1.32 + 0.75 for example).
1.33 +
1.34 +config NICE
1.35 + int
1.36 + prompt "Nice level"
1.37 + default 0
1.38 + range 0 19
1.39 + help
1.40 + Renices the build process up.
1.41 +
1.42 +config USE_PIPES
1.43 + bool
1.44 + prompt "Use -pipe"
1.45 + default y
1.46 + help
1.47 + Use gcc's option -pipe to use pipes rather than temp files when building
1.48 + the toolchain.
2.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
2.2 +++ b/config/ct-behave.in Thu Apr 17 20:02:07 2008 +0000
2.3 @@ -0,0 +1,82 @@
2.4 +# Options specific to crosstool-NG overall behavior
2.5 +
2.6 +comment "crosstool-NG behavior"
2.7 +
2.8 +config OBSOLETE
2.9 + bool
2.10 + prompt "Use obsolete features"
2.11 + default n
2.12 + help
2.13 + If you set this to Y, you will be able to select obsolete features.
2.14 +
2.15 + Such obsolete features are the use of old kernel headers, old
2.16 + gcc versions, etc...
2.17 +
2.18 +config EXPERIMENTAL
2.19 + bool
2.20 + prompt "Try features marked as EXPERIMENTAL"
2.21 + default n
2.22 + help
2.23 + If you set this to Y, then you will be able to try very experimental
2.24 + features.
2.25 +
2.26 + Experimental features can be one of:
2.27 + - working, in which case you should tell me it is!
2.28 + - buggy, in which case you could try patching and send me the result
2.29 + - unfinished, in which case you could try hacking it and send me the result
2.30 + - non-existant, in which case you could also try hacking it in and send me
2.31 + the result
2.32 +
2.33 +config BROKEN
2.34 + bool
2.35 + prompt "Try broken stuff"
2.36 + default n
2.37 + depends on EXPERIMENTAL
2.38 + help
2.39 + Select this if you want to _debug_ broken stuff.
2.40 +
2.41 +config DEBUG_CT
2.42 + bool
2.43 + prompt "Debug crosstool-NG"
2.44 + default n
2.45 + help
2.46 + Say 'y' here to get some debugging options
2.47 +
2.48 +if DEBUG_CT
2.49 +
2.50 +config DEBUG_CT_PAUSE_STEPS
2.51 + bool
2.52 + prompt "Pause between every steps"
2.53 + default n
2.54 + help
2.55 + Say 'y' if you intend to attend the build, and want to investigate
2.56 + the result of each steps before running the next one.
2.57 +
2.58 +config DEBUG_CT_SAVE_STEPS
2.59 + bool
2.60 + prompt "Save intermediate steps"
2.61 + default n
2.62 + help
2.63 + If you say 'y' here, then you will be able to restart crosstool-NG at
2.64 + any step.
2.65 +
2.66 + It is not currently possible to restart at any of the debug facility.
2.67 + They are treated as a whole.
2.68 +
2.69 + See docs/overview.txt for the list of steps.
2.70 +
2.71 +config DEBUG_CT_SAVE_STEPS_GZIP
2.72 + bool
2.73 + prompt "gzip saved states"
2.74 + default y
2.75 + depends on DEBUG_CT_SAVE_STEPS
2.76 + help
2.77 + If you are tight on space, then you can ask to gzip the saved states
2.78 + tarballs. On the other hand, this takes some longer time...
2.79 +
2.80 + To lose as less time as possible, the gzip process is done with a low
2.81 + compression ratio (-3), which gives roughly 70% gain in size. Going
2.82 + further doesn't gain much, and takes far more time (believe me, I've
2.83 + got figures here! :-) ).
2.84 +
2.85 +endif
3.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
3.2 +++ b/config/download_extract.in Thu Apr 17 20:02:07 2008 +0000
3.3 @@ -0,0 +1,171 @@
3.4 +# Options specific to downloading and extracting packages
3.5 +
3.6 +comment "Downloading"
3.7 +
3.8 +config FORCE_DOWNLOAD
3.9 + bool
3.10 + prompt "Force downloads"
3.11 + default n
3.12 + help
3.13 + Force downloading tarballs, even if one already exists.
3.14 +
3.15 + Usefull if you suspect a tarball to be damaged.
3.16 +
3.17 +config ONLY_DOWNLOAD
3.18 + bool
3.19 + prompt "Stop after downloading tarballs"
3.20 + default n
3.21 + help
3.22 + Only download the tarballs. Exit once it done.
3.23 +
3.24 + Usefull to pre-retrieve the tarballs before going off-line.
3.25 +
3.26 +choice
3.27 + bool
3.28 + prompt "Proxy type"
3.29 + default USE_NO_PROXY
3.30 +
3.31 +config PROXY_TYPE_NONE
3.32 + bool
3.33 + prompt "No proxy"
3.34 + help
3.35 + Select this option if you have a direct connection to the internet,
3.36 + or if you already set the environment adequately.
3.37 +
3.38 +config PROXY_TYPE_HTTP
3.39 + bool
3.40 + prompt "HTTP proxy"
3.41 + help
3.42 + Use an HTTP proxy to connect to to the internet.
3.43 + Only the http and ftp protocols will be tunneled through this
3.44 + proxy.
3.45 +
3.46 + Alternatively to setting this option, you can set and export the
3.47 + following variables in your environment:
3.48 + ftp_proxy=http://user:passwd@proxy.server:port/
3.49 + http_proxy=http://user:passwd@proxy.server:port/
3.50 + https_proxy=http://user:passwd@proxy.server:port/
3.51 +
3.52 +# Haha! Here is an interesting feature/bug of mconf!
3.53 +# The following config entries will be shown out-side the
3.54 +# choice menu!
3.55 +# To add a third entry in the choice menu, add it after the
3.56 +# if...endif conditional below, and so on for a fourth entry...
3.57 +if PROXY_TYPE_HTTP
3.58 +
3.59 +config PROXY_HOST
3.60 + string
3.61 + prompt "hostname/IP"
3.62 +
3.63 +config PROXY_PORT
3.64 + int
3.65 + prompt "port"
3.66 + default 0
3.67 +
3.68 +config PROXY_USER
3.69 + string
3.70 + prompt "user name"
3.71 +
3.72 +config PROXY_PASS
3.73 + string
3.74 + prompt "password"
3.75 +
3.76 +endif # USE_HTTP_PROXY
3.77 +
3.78 +config PROXY_TYPE_SOCKS
3.79 + bool
3.80 + prompt "SOCKS 4/5 proxy"
3.81 + help
3.82 + Use a Socks 4/5 proxy to connect to the internet.
3.83 + All protocols can get tunneled through this kind of proxy (depending
3.84 + on your proxy configuration, so;e do not allow all protocols, but
3.85 + chances are that protocols needed by crosstool-NG are allowed).
3.86 +
3.87 + Alternatively to setting this option, you can set and export the
3.88 + following variable in your environment:
3.89 + LD_PRELOAD=/path/to/your/tsocks-library.so
3.90 +
3.91 + In any case, wether you set this option or you export the aforementionned
3.92 + variable, you will _have_ to configure the /etc/tsocks.conf file
3.93 + accordingly to your network setup.
3.94 +
3.95 + This option makes use of the tsocks library. You will have to have tsocks
3.96 + installed on your system, of course.
3.97 +
3.98 + If you think you do not know what tsocks is, or how to configure it,
3.99 + chances are that you do not need to set this option.
3.100 +
3.101 +if PROXY_TYPE_SOCKS
3.102 +
3.103 +choice
3.104 + bool
3.105 + prompt "type"
3.106 + default PROXY_TYPE_SOCKS_5
3.107 +
3.108 +config PROXY_TYPE_SOCKS_5
3.109 + bool
3.110 + prompt "SOCKS 5"
3.111 +
3.112 +config PROXY_TYPE_SOCKS_4
3.113 + bool
3.114 + prompt "SOCKS 4"
3.115 +
3.116 +endchoice
3.117 +
3.118 +config PROXY_HOST
3.119 + string
3.120 + prompt "hostname/IP"
3.121 +
3.122 +config PROXY_PORT
3.123 + int
3.124 + prompt "port"
3.125 + default 0
3.126 +
3.127 +config PROXY_USER
3.128 + string
3.129 + prompt "user name"
3.130 +
3.131 +config PROXY_PASS
3.132 + string
3.133 + prompt "password"
3.134 +
3.135 +endif # USE_SOCKS_PROXY
3.136 +
3.137 +endchoice
3.138 +
3.139 +config PROXY_TYPE
3.140 + string
3.141 + default "none" if PROXY_TYPE_NONE
3.142 + default "HTTP" if PROXY_TYPE_HTTP
3.143 + default "socks5" if PROXY_TYPE_SOCKS_5
3.144 + default "socks4" if PROXY_TYPE_SOCKS_4
3.145 +
3.146 +# Force restore indentation
3.147 +config BREAK_INDENT
3.148 + bool
3.149 + default n
3.150 +
3.151 +if ! ONLY_DOWNLOAD
3.152 +
3.153 +comment "Extracting"
3.154 +
3.155 +config FORCE_EXTRACT
3.156 + bool
3.157 + prompt "Force extractions"
3.158 + default n
3.159 + help
3.160 + Force extraction of already exctracted tarballs.
3.161 +
3.162 + Usefull if you suspect a previous extract did not complete (eg. broken
3.163 + tarball), or you added a new set of patches for this component.
3.164 +
3.165 +config ONLY_EXTRACT
3.166 + bool
3.167 + prompt "Stop after extracting tarballs"
3.168 + default n
3.169 + help
3.170 + Exit after unpacking and patching tarballs.
3.171 +
3.172 + Usefull to look at the code before doing the build itself.
3.173 +
3.174 +endif # ! ONLY_DOWNLOAD
4.1 --- a/config/global.in Thu Apr 17 19:21:32 2008 +0000
4.2 +++ b/config/global.in Thu Apr 17 20:02:07 2008 +0000
4.3 @@ -1,506 +1,11 @@
4.4 # Overall toolchain configuration: paths, jobs, etc...
4.5
4.6 -# Ah, this option is here to break the dependency tracking, and allow
4.7 -# dependent option to line-up with the options they depend on ,rather
4.8 -# than being indented
4.9 -# Use it to intersperse two config options depending one on the other,
4.10 -# but don't want the second to be indented (for example because you have
4.11 -# a comment between the two to separate them). See DOWNLOAD and EXTRACT
4.12 -# options to see how it is used.
4.13 -config FOOBAR
4.14 - bool
4.15 - default n
4.16 -
4.17 menu "Paths and misc options"
4.18
4.19 -comment "crosstool-NG behavior"
4.20 -
4.21 -config OBSOLETE
4.22 - bool
4.23 - prompt "Use obsolete features"
4.24 - default n
4.25 - help
4.26 - If you set this to Y, you will be able to select obsolete features.
4.27 -
4.28 - Such obsolete features are the use of old kernel headers, old
4.29 - gcc versions, etc...
4.30 -
4.31 -config EXPERIMENTAL
4.32 - bool
4.33 - prompt "Try features marked as EXPERIMENTAL"
4.34 - default n
4.35 - help
4.36 - If you set this to Y, then you will be able to try very experimental
4.37 - features.
4.38 -
4.39 - Experimental features can be one of:
4.40 - - working, in which case you should tell me it is!
4.41 - - buggy, in which case you could try patching and send me the result
4.42 - - unfinished, in which case you could try hacking it and send me the result
4.43 - - non-existant, in which case you could also try hacking it in and send me
4.44 - the result
4.45 -
4.46 -config BROKEN
4.47 - bool
4.48 - prompt "Try broken stuff"
4.49 - default n
4.50 - depends on EXPERIMENTAL
4.51 - help
4.52 - Select this if you want to _debug_ broken stuff.
4.53 -
4.54 -config DEBUG_CT
4.55 - bool
4.56 - prompt "Debug crosstool-NG"
4.57 - default n
4.58 - help
4.59 - Say 'y' here to get some debugging options
4.60 -
4.61 -if DEBUG_CT
4.62 -
4.63 -config DEBUG_CT_PAUSE_STEPS
4.64 - bool
4.65 - prompt "Pause between every steps"
4.66 - default n
4.67 - help
4.68 - Say 'y' if you intend to attend the build, and want to investigate
4.69 - the result of each steps before running the next one.
4.70 -
4.71 -config DEBUG_CT_SAVE_STEPS
4.72 - bool
4.73 - prompt "Save intermediate steps"
4.74 - default n
4.75 - help
4.76 - If you say 'y' here, then you will be able to restart crosstool-NG at
4.77 - any step.
4.78 -
4.79 - It is not currently possible to rstart at any of the debug facility.
4.80 - They are treated as a whole.
4.81 -
4.82 - See docs/overview.txt for the list of steps.
4.83 -
4.84 -config DEBUG_CT_SAVE_STEPS_GZIP
4.85 - bool
4.86 - prompt "gzip saved states"
4.87 - default y
4.88 - depends on DEBUG_CT_SAVE_STEPS
4.89 - help
4.90 - If you are tight on space, then you can ask to gzip the saved states
4.91 - tarballs. On the other hand, this takes some longer time...
4.92 -
4.93 - To lose as less time as possible, the gzip process is done with a low
4.94 - compression ratio (-3), which gives roughly 70% gain in size. Going
4.95 - further doesn't gain much, and takes far more time (believe me, I've
4.96 - got figures here! :-) ).
4.97 -
4.98 -endif
4.99 -
4.100 -comment "Build behavior"
4.101 -
4.102 -config PARALLEL_JOBS
4.103 - int
4.104 - prompt "Number of parallel jobs"
4.105 - default 1
4.106 - help
4.107 - Number of jobs make will be allowed to run concurently.
4.108 - Set this higher than the number of processors you have, but not too high.
4.109 - A good rule of thumb is twice the number of processors you have.
4.110 -
4.111 - Enter 1 (or 0) to have only one job at a time.
4.112 -
4.113 -config LOAD
4.114 - int
4.115 - prompt "Maximum allowed load"
4.116 - default 0
4.117 - help
4.118 - Specifies that no new jobs should be started if there are others jobs
4.119 - running and the load average is at least this value.
4.120 -
4.121 - Makes sense on SMP machines only.
4.122 -
4.123 - Enter 0 to have no limit on the load average.
4.124 -
4.125 - Note: only the integer part of the load is allowed here (you can't enter
4.126 - 0.75 for example).
4.127 -
4.128 -config NICE
4.129 - int
4.130 - prompt "Nice level"
4.131 - default 0
4.132 - range 0 19
4.133 - help
4.134 - Renices the build process up.
4.135 -
4.136 -config USE_PIPES
4.137 - bool
4.138 - prompt "Use -pipe"
4.139 - default y
4.140 - help
4.141 - Use gcc's option -pipe to use pipes rather than temp files when building
4.142 - the toolchain.
4.143 -
4.144 -comment "Paths"
4.145 -
4.146 -config LOCAL_TARBALLS_DIR
4.147 - string
4.148 - prompt "Local tarballs directory"
4.149 - default ""
4.150 - help
4.151 - If you have previously downloaded the tarballs, enter the PATH where
4.152 - you stored them here.
4.153 -
4.154 -config SAVE_TARBALLS
4.155 - bool
4.156 - prompt "Save new tarballs"
4.157 - default n
4.158 - depends on LOCAL_TARBALLS_DIR != ""
4.159 - help
4.160 - If you say 'y' here, new downloaded tarballs will be saved in the
4.161 - directory you entered above.
4.162 -
4.163 -config PREFIX_DIR
4.164 - string
4.165 - prompt "Prefix directory"
4.166 - default "${HOME}/${CT_TARGET}"
4.167 - help
4.168 - This is the path the toolchain will run from.
4.169 -
4.170 -config INSTALL_DIR
4.171 - string
4.172 -# prompt "Install directory"
4.173 - default "${CT_PREFIX_DIR}"
4.174 -# help
4.175 -# This is the path the target will be installed into.
4.176 -#
4.177 -# Normally, you would set this to ${CT_PREFIX_DIR}, but if for some reasons
4.178 -# you can't write there, you can install somewhere else and have a third
4.179 -# person do the install for you.
4.180 -# The reason you might also want to install elsewhere is if you are going
4.181 -# to package your shinny new toolchain for distribution.
4.182 -
4.183 -config CUSTOM_PATCH
4.184 - bool
4.185 - prompt "Use custom patch directory"
4.186 - default n
4.187 - help
4.188 - If you have custom patches that you want to be applied, say 'Y' here and
4.189 - enter the path directory below.
4.190 -
4.191 - Note that you must ensure that the patch directory is arranged the same
4.192 - way the official directory is.
4.193 -
4.194 -config CUSTOM_PATCH_ONLY
4.195 - bool
4.196 - prompt "Only use custom patches"
4.197 - default n
4.198 - depends on CUSTOM_PATCH
4.199 - help
4.200 - Don't apply patches coming with crosstool-NG, only those patches available
4.201 - in the directory below.
4.202 -
4.203 - If you say 'N' here, then the patches provided with crosstool-NG will be
4.204 - applied first, and then your patches.
4.205 -
4.206 -config CUSTOM_PATCH_DIR
4.207 - string
4.208 - prompt "Custom patch directory"
4.209 - default ""
4.210 - depends on CUSTOM_PATCH
4.211 - help
4.212 - Enter the custom patch directory here.
4.213 -
4.214 -config REMOVE_DOCS
4.215 - bool
4.216 - prompt "Remove documentation"
4.217 - default n
4.218 - help
4.219 - Remove the installed documentation (man and info pages).
4.220 - Gains around 8MiB for a uClibc-based, C and C++ compiler.
4.221 -
4.222 -config INSTALL_DIR_RO
4.223 - bool
4.224 - prompt "Render the toolchain read-only"
4.225 - default n
4.226 - help
4.227 - Render the directory of the toolchain (and its sub-directories)
4.228 - read-only.
4.229 -
4.230 - Usefull for toolchains destined for production.
4.231 -
4.232 -comment "Downloading"
4.233 -
4.234 -config FORCE_DOWNLOAD
4.235 - bool
4.236 - prompt "Force downloads"
4.237 - default n
4.238 - help
4.239 - Force downloading tarballs, even if one already exists.
4.240 -
4.241 - Usefull if you suspect a tarball to be damaged.
4.242 -
4.243 -config ONLY_DOWNLOAD
4.244 - bool
4.245 - prompt "Stop after downloading tarballs"
4.246 - default n
4.247 - help
4.248 - Only download the tarballs. Exit once it done.
4.249 -
4.250 - Usefull to pre-retrieve the tarballs before going off-line.
4.251 -
4.252 -choice
4.253 - bool
4.254 - prompt "Proxy type"
4.255 - default USE_NO_PROXY
4.256 -
4.257 -config PROXY_TYPE_NONE
4.258 - bool
4.259 - prompt "No proxy"
4.260 - help
4.261 - Select this option if you have a direct connection to the internet,
4.262 - or if you already set the environment adequately.
4.263 -
4.264 -config PROXY_TYPE_HTTP
4.265 - bool
4.266 - prompt "HTTP proxy"
4.267 - help
4.268 - Use an HTTP proxy to connect to to the internet.
4.269 - Only the http and ftp protocols will be tunneled through this
4.270 - proxy.
4.271 -
4.272 - Alternatively to setting this option, you can set and export the
4.273 - following variables in your environment:
4.274 - ftp_proxy=http://user:passwd@proxy.server:port/
4.275 - http_proxy=http://user:passwd@proxy.server:port/
4.276 - https_proxy=http://user:passwd@proxy.server:port/
4.277 -
4.278 -# Haha! Here is an interesting feature/bug of mconf!
4.279 -# The following config entries will be shown out-side the
4.280 -# choice menu!
4.281 -# To add a third entry in the choice menu, add it after the
4.282 -# if...endif conditional below, and so on for a fourth entry...
4.283 -if PROXY_TYPE_HTTP
4.284 -
4.285 -config PROXY_HOST
4.286 - string
4.287 - prompt "hostname/IP"
4.288 -
4.289 -config PROXY_PORT
4.290 - int
4.291 - prompt "port"
4.292 - default 0
4.293 -
4.294 -config PROXY_USER
4.295 - string
4.296 - prompt "user name"
4.297 -
4.298 -config PROXY_PASS
4.299 - string
4.300 - prompt "password"
4.301 -
4.302 -endif # USE_HTTP_PROXY
4.303 -
4.304 -config PROXY_TYPE_SOCKS
4.305 - bool
4.306 - prompt "SOCKS 4/5 proxy"
4.307 - help
4.308 - Use a Socks 4/5 proxy to connect to the internet.
4.309 - All protocols can get tunneled through this kind of proxy (depending
4.310 - on your proxy configuration, so;e do not allow all protocols, but
4.311 - chances are that protocols needed by crosstool-NG are allowed).
4.312 -
4.313 - Alternatively to setting this option, you can set and export the
4.314 - following variable in your environment:
4.315 - LD_PRELOAD=/path/to/your/tsocks-library.so
4.316 -
4.317 - In any case, wether you set this option or you export the aforementionned
4.318 - variable, you will _have_ to configure the /etc/tsocks.conf file
4.319 - accordingly to your network setup.
4.320 -
4.321 - This option makes use of the tsocks library. You will have to have tsocks
4.322 - installed on your system, of course.
4.323 -
4.324 - If you think you do not know what tsocks is, or how to configure it,
4.325 - chances are that you do not need to set this option.
4.326 -
4.327 -if PROXY_TYPE_SOCKS
4.328 -
4.329 -choice
4.330 - bool
4.331 - prompt "type"
4.332 - default PROXY_TYPE_SOCKS_5
4.333 -
4.334 -config PROXY_TYPE_SOCKS_5
4.335 - bool
4.336 - prompt "SOCKS 5"
4.337 -
4.338 -config PROXY_TYPE_SOCKS_4
4.339 - bool
4.340 - prompt "SOCKS 4"
4.341 -
4.342 -endchoice
4.343 -
4.344 -config PROXY_HOST
4.345 - string
4.346 - prompt "hostname/IP"
4.347 -
4.348 -config PROXY_PORT
4.349 - int
4.350 - prompt "port"
4.351 - default 0
4.352 -
4.353 -config PROXY_USER
4.354 - string
4.355 - prompt "user name"
4.356 -
4.357 -config PROXY_PASS
4.358 - string
4.359 - prompt "password"
4.360 -
4.361 -endif # USE_SOCKS_PROXY
4.362 -
4.363 -endchoice
4.364 -
4.365 -config PROXY_TYPE
4.366 - string
4.367 - default "none" if PROXY_TYPE_NONE
4.368 - default "HTTP" if PROXY_TYPE_HTTP
4.369 - default "socks5" if PROXY_TYPE_SOCKS_5
4.370 - default "socks4" if PROXY_TYPE_SOCKS_4
4.371 -
4.372 -# Force restore indentation
4.373 -config FOOBAR
4.374 -
4.375 -if ! ONLY_DOWNLOAD
4.376 -
4.377 -comment "Extracting"
4.378 -
4.379 -config FORCE_EXTRACT
4.380 - bool
4.381 - prompt "Force extractions"
4.382 - default n
4.383 - help
4.384 - Force extraction of already exctracted tarballs.
4.385 -
4.386 - Usefull if you suspect a previous extract did not complete (eg. broken
4.387 - tarball), or you added a new set of patches for this component.
4.388 -
4.389 -config ONLY_EXTRACT
4.390 - bool
4.391 - prompt "Stop after extracting tarballs"
4.392 - default n
4.393 - help
4.394 - Exit after unpacking and patching tarballs.
4.395 -
4.396 - Usefull to look at the code before doing the build itself.
4.397 -
4.398 -endif # ! ONLY_DOWNLOAD
4.399 -
4.400 -comment "Logging"
4.401 -
4.402 -choice
4.403 - bool
4.404 - prompt "Maximum log level to see:"
4.405 - default LOG_INFO if !DEBUG_CT
4.406 - default LOG_DEBUG if DEBUG_CT
4.407 -
4.408 -config LOG_ERROR
4.409 - bool
4.410 - prompt "ERROR"
4.411 - help
4.412 - The build will be silent.
4.413 - Only if there is an error will you see a message.
4.414 -
4.415 -config LOG_WARN
4.416 - bool
4.417 - prompt "WARN"
4.418 - help
4.419 - The same as above, plus warnings.
4.420 -
4.421 -config LOG_INFO
4.422 - bool
4.423 - prompt "INFO"
4.424 - help
4.425 - The same as above, plus informational messages (main steps).
4.426 -
4.427 -config LOG_EXTRA
4.428 - bool
4.429 - prompt "EXTRA"
4.430 - help
4.431 - The same as above, plus extra messages (sub-steps).
4.432 -
4.433 -config LOG_DEBUG
4.434 - bool
4.435 - prompt "DEBUG"
4.436 - help
4.437 - The same as above, plus lots of crosstool-NG debug information.
4.438 -
4.439 -config LOG_ALL
4.440 - bool
4.441 - prompt "ALL"
4.442 - help
4.443 - The same as above, plus all components build messages (very noisy!).
4.444 -
4.445 -endchoice
4.446 -
4.447 -config LOG_LEVEL_MAX
4.448 - string
4.449 - default "ERROR" if LOG_ERROR
4.450 - default "WARN" if LOG_WARN
4.451 - default "INFO" if LOG_INFO
4.452 - default "EXTRA" if LOG_EXTRA
4.453 - default "DEBUG" if LOG_DEBUG
4.454 - default "ALL" if LOG_ALL
4.455 -
4.456 -config LOG_SEE_TOOLS_WARN
4.457 - bool
4.458 - prompt "Warnings from the tools' builds"
4.459 - default n
4.460 - depends on ! LOG_ERROR
4.461 - help
4.462 - Treat warnings from the different tools as crosstool-NG warnings.
4.463 - If you say 'y' here, then those warnings will be prefixed with
4.464 - '[WARN ]' instead of the default '[ALL ]'.
4.465 -
4.466 - You can safely say 'n' here. Those warnings will anyway be
4.467 - recorded in the log file (provided you configured one).
4.468 -
4.469 - Tools error will always be logged as crosstool-NG errors.
4.470 -
4.471 -config LOG_PROGRESS_BAR
4.472 - bool
4.473 - prompt "Progress bar"
4.474 - default y
4.475 - depends on ! LOG_ALL
4.476 - help
4.477 - If you say 'y' here, you'll be able to see the elapsed time.
4.478 -
4.479 - As a bonus, you'll also get a rotating bar (/-\|) showing you
4.480 - that the build is not stalled (the bar rotates 1/4 every 10 lines
4.481 - of components build log).
4.482 -
4.483 - Note that the elapsed time can stall for a little while if a
4.484 - component has long commands, as the elapsed time is only updated
4.485 - each line.
4.486 -
4.487 -config LOG_TO_FILE
4.488 - bool
4.489 - prompt "Log to a file"
4.490 - default y
4.491 - help
4.492 - Save *full* logs to a file. Even log levels you didn't specify above
4.493 - will be available in this file. The log file will be named build.log
4.494 - and stored in the toolchain prefix dir (set above).
4.495 -
4.496 - As a bonus, there is a script in tools/extractConfig.sh that is able
4.497 - to extract the configuration of crosstool-NG from the log file.
4.498 -
4.499 - Definitely, say Y.
4.500 -
4.501 -config LOG_FILE_COMPRESS
4.502 - bool
4.503 - prompt "Compress the log file"
4.504 - default n
4.505 - depends on LOG_TO_FILE
4.506 - help
4.507 - Compress the log file once the toolchain is successfully built.
4.508 +source "config/ct-behave.in"
4.509 +source "config/download_extract.in"
4.510 +source "config/build-behave.in"
4.511 +source "config/paths.in"
4.512 +source "config/logging.in"
4.513
4.514 endmenu
5.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
5.2 +++ b/config/logging.in Thu Apr 17 20:02:07 2008 +0000
5.3 @@ -0,0 +1,110 @@
5.4 +# Options specific to logging
5.5 +
5.6 +comment "Logging"
5.7 +
5.8 +choice
5.9 + bool
5.10 + prompt "Maximum log level to see:"
5.11 + default LOG_INFO if !DEBUG_CT
5.12 + default LOG_DEBUG if DEBUG_CT
5.13 +
5.14 +config LOG_ERROR
5.15 + bool
5.16 + prompt "ERROR"
5.17 + help
5.18 + The build will be silent.
5.19 + Only if there is an error will you see a message.
5.20 +
5.21 +config LOG_WARN
5.22 + bool
5.23 + prompt "WARN"
5.24 + help
5.25 + The same as above, plus warnings.
5.26 +
5.27 +config LOG_INFO
5.28 + bool
5.29 + prompt "INFO"
5.30 + help
5.31 + The same as above, plus informational messages (main steps).
5.32 +
5.33 +config LOG_EXTRA
5.34 + bool
5.35 + prompt "EXTRA"
5.36 + help
5.37 + The same as above, plus extra messages (sub-steps).
5.38 +
5.39 +config LOG_DEBUG
5.40 + bool
5.41 + prompt "DEBUG"
5.42 + help
5.43 + The same as above, plus lots of crosstool-NG debug information.
5.44 +
5.45 +config LOG_ALL
5.46 + bool
5.47 + prompt "ALL"
5.48 + help
5.49 + The same as above, plus all components build messages (very noisy!).
5.50 +
5.51 +endchoice
5.52 +
5.53 +config LOG_LEVEL_MAX
5.54 + string
5.55 + default "ERROR" if LOG_ERROR
5.56 + default "WARN" if LOG_WARN
5.57 + default "INFO" if LOG_INFO
5.58 + default "EXTRA" if LOG_EXTRA
5.59 + default "DEBUG" if LOG_DEBUG
5.60 + default "ALL" if LOG_ALL
5.61 +
5.62 +config LOG_SEE_TOOLS_WARN
5.63 + bool
5.64 + prompt "Warnings from the tools' builds"
5.65 + default n
5.66 + depends on ! LOG_ERROR
5.67 + help
5.68 + Treat warnings from the different tools as crosstool-NG warnings.
5.69 + If you say 'y' here, then those warnings will be prefixed with
5.70 + '[WARN ]' instead of the default '[ALL ]'.
5.71 +
5.72 + You can safely say 'n' here. Those warnings will anyway be
5.73 + recorded in the log file (provided you configured one).
5.74 +
5.75 + Tools error will always be logged as crosstool-NG errors.
5.76 +
5.77 +config LOG_PROGRESS_BAR
5.78 + bool
5.79 + prompt "Progress bar"
5.80 + default y
5.81 + depends on ! LOG_ALL
5.82 + help
5.83 + If you say 'y' here, you'll be able to see the elapsed time.
5.84 +
5.85 + As a bonus, you'll also get a rotating bar (/-\|) showing you
5.86 + that the build is not stalled (the bar rotates 1/4 every 10 lines
5.87 + of components build log).
5.88 +
5.89 + Note that the elapsed time can stall for a little while if a
5.90 + component has long commands, as the elapsed time is only updated
5.91 + each line.
5.92 +
5.93 +config LOG_TO_FILE
5.94 + bool
5.95 + prompt "Log to a file"
5.96 + default y
5.97 + help
5.98 + Save *full* logs to a file. Even log levels you didn't specify above
5.99 + will be available in this file. The log file will be named build.log
5.100 + and stored in the toolchain prefix dir (set above).
5.101 +
5.102 + As a bonus, there is a script in tools/extractConfig.sh that is able
5.103 + to extract the configuration of crosstool-NG from the log file.
5.104 +
5.105 + Definitely, say Y.
5.106 +
5.107 +config LOG_FILE_COMPRESS
5.108 + bool
5.109 + prompt "Compress the log file"
5.110 + default n
5.111 + depends on LOG_TO_FILE
5.112 + help
5.113 + Compress the log file once the toolchain is successfully built.
6.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
6.2 +++ b/config/paths.in Thu Apr 17 20:02:07 2008 +0000
6.3 @@ -0,0 +1,89 @@
6.4 +# Options related to paths and install
6.5 +
6.6 +comment "Paths"
6.7 +
6.8 +config LOCAL_TARBALLS_DIR
6.9 + string
6.10 + prompt "Local tarballs directory"
6.11 + default ""
6.12 + help
6.13 + If you have previously downloaded the tarballs, enter the PATH where
6.14 + you stored them here.
6.15 +
6.16 +config SAVE_TARBALLS
6.17 + bool
6.18 + prompt "Save new tarballs"
6.19 + default n
6.20 + depends on LOCAL_TARBALLS_DIR != ""
6.21 + help
6.22 + If you say 'y' here, new downloaded tarballs will be saved in the
6.23 + directory you entered above.
6.24 +
6.25 +config PREFIX_DIR
6.26 + string
6.27 + prompt "Prefix directory"
6.28 + default "${HOME}/${CT_TARGET}"
6.29 + help
6.30 + This is the path the toolchain will run from.
6.31 +
6.32 +config INSTALL_DIR
6.33 + string
6.34 +# prompt "Install directory"
6.35 + default "${CT_PREFIX_DIR}"
6.36 +# help
6.37 +# This is the path the target will be installed into.
6.38 +#
6.39 +# Normally, you would set this to ${CT_PREFIX_DIR}, but if for some reasons
6.40 +# you can't write there, you can install somewhere else and have a third
6.41 +# person do the install for you.
6.42 +# The reason you might also want to install elsewhere is if you are going
6.43 +# to package your shinny new toolchain for distribution.
6.44 +
6.45 +config CUSTOM_PATCH
6.46 + bool
6.47 + prompt "Use custom patch directory"
6.48 + default n
6.49 + help
6.50 + If you have custom patches that you want to be applied, say 'Y' here and
6.51 + enter the path directory below.
6.52 +
6.53 + Note that you must ensure that the patch directory is arranged the same
6.54 + way the official directory is.
6.55 +
6.56 +config CUSTOM_PATCH_ONLY
6.57 + bool
6.58 + prompt "Only use custom patches"
6.59 + default n
6.60 + depends on CUSTOM_PATCH
6.61 + help
6.62 + Don't apply patches coming with crosstool-NG, only those patches available
6.63 + in the directory below.
6.64 +
6.65 + If you say 'N' here, then the patches provided with crosstool-NG will be
6.66 + applied first, and then your patches.
6.67 +
6.68 +config CUSTOM_PATCH_DIR
6.69 + string
6.70 + prompt "Custom patch directory"
6.71 + default ""
6.72 + depends on CUSTOM_PATCH
6.73 + help
6.74 + Enter the custom patch directory here.
6.75 +
6.76 +config REMOVE_DOCS
6.77 + bool
6.78 + prompt "Remove documentation"
6.79 + default n
6.80 + help
6.81 + Remove the installed documentation (man and info pages).
6.82 + Gains around 8MiB for a uClibc-based, C and C++ compiler.
6.83 +
6.84 +config INSTALL_DIR_RO
6.85 + bool
6.86 + prompt "Render the toolchain read-only"
6.87 + default n
6.88 + help
6.89 + Render the directory of the toolchain (and its sub-directories)
6.90 + read-only.
6.91 +
6.92 + Usefull for toolchains destined for production.