1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/config/global.in Sat Feb 24 11:00:05 2007 +0000
1.3 @@ -0,0 +1,256 @@
1.4 +# Overall toolchain configuration: paths, jobs, etc...
1.5 +
1.6 +menu "Paths and misc options"
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.
1.49 +
1.50 +comment "Paths"
1.51 +
1.52 +config TARBALLS_DIR
1.53 + string
1.54 + prompt "Tarballs directory"
1.55 + default "`pwd`/tarballs"
1.56 + help
1.57 + This is the directory into which tarballs are going to be stored once
1.58 + they are downloaded (or otherwise retrieved).
1.59 +
1.60 +config SRC_DIR
1.61 + string
1.62 + prompt "Extract directory"
1.63 + default "`pwd`/${CT_TARGET}/src"
1.64 + help
1.65 + This is the directory into which tarballs will be extracted.
1.66 +
1.67 + If you will build multiple toolchains, you should arrange to have one
1.68 + SRC_DIR for each toolchain, as different targets may require different
1.69 + patches to be applied.
1.70 +
1.71 +config BUILD_DIR
1.72 + string
1.73 + prompt "Build directory"
1.74 + default "`pwd`/${CT_TARGET}/gcc-${CT_CC_VERSION}-${CT_LIBC}-${CT_LIBC_VERSION}"
1.75 + help
1.76 + This is the directory into which builds will occur.
1.77 +
1.78 + Once again, arrange for one build directory for each toolchain you build,
1.79 + to avoid collision.
1.80 +
1.81 +config PREFIX_DIR
1.82 + string
1.83 + prompt "Prefix directory"
1.84 + default "${HOME}/${CT_TARGET}"
1.85 + help
1.86 + This is the path the toolchain will run from.
1.87 +
1.88 +config INSTALL_DIR
1.89 + string
1.90 +# prompt "Install directory"
1.91 + default "${CT_PREFIX_DIR}"
1.92 +# help
1.93 +# This is the path the target will be installed into.
1.94 +#
1.95 +# Normally, you would set this to ${CT_PREFIX_DIR}, but if for some reasons
1.96 +# you can't write there, you can install somewhere else and have a third
1.97 +# person do the install for you.
1.98 +# The reason you might also want to install elsewhere is if you are going
1.99 +# to package your shinny new toolchain for distribution.
1.100 +
1.101 +config CUSTOM_PATCH
1.102 + bool
1.103 + prompt "Use custom patch directory"
1.104 + default n
1.105 + help
1.106 + If you have custom patches that you want to be applied, say 'Y' here and
1.107 + enter the path directory below.
1.108 +
1.109 + Note that you must ensure that the patch directory is arranged the same
1.110 + way the official directory is.
1.111 +
1.112 +config CUSTOM_PATCH_ONLY
1.113 + bool
1.114 + prompt "Only use custom patches"
1.115 + default n
1.116 + depends on CUSTOM_PATCH
1.117 + help
1.118 + Don't apply patches coming with CT-NG, only those patches available in
1.119 + the directory below.
1.120 +
1.121 + If you say 'N' here, then the patches provided with CT-NG will be applied
1.122 + first, and then your patches.
1.123 +
1.124 +config CUSTOM_PATCH_DIR
1.125 + string
1.126 + prompt "Custom patch directory"
1.127 + default ""
1.128 + depends on CUSTOM_PATCH
1.129 + help
1.130 + Enter the custom patch directory here.
1.131 +
1.132 +comment "Downloading and extracting"
1.133 +
1.134 +config NO_DOWNLOAD
1.135 + bool
1.136 + prompt "Avoid downloads"
1.137 + default n
1.138 + help
1.139 + Avoid downloading anything. Bail out if a tarball is missing.
1.140 +
1.141 +config ONLY_DOWNLOAD
1.142 + bool
1.143 + prompt "Only download tarballs"
1.144 + default n
1.145 + depends on ! NO_DOWNLOAD
1.146 + help
1.147 + Only download the tarballs. Exit once it done.
1.148 +
1.149 + Usefull to pre-retrieve the tarballs before going off-line.
1.150 +
1.151 +config FORCE_DOWNLOAD
1.152 + bool
1.153 + prompt "Force downloads"
1.154 + default n
1.155 + depends on ! NO_DOWNLOAD
1.156 + help
1.157 + Force downloading tarballs, even if one already exists.
1.158 + Usefull if you suspect a tarball to be damaged.
1.159 +
1.160 +config FORCE_EXTRACT
1.161 + bool
1.162 + prompt "Force extractions"
1.163 + depends on ! ONLY_DOWNLOAD
1.164 + default n
1.165 + help
1.166 + Force extraction of already exctracted tarballs.
1.167 +
1.168 + Usefull if you suspect a previous extract did not complete (eg. broken
1.169 + tarball), or you added a new set of patches for this component.
1.170 +
1.171 +comment "Logging"
1.172 +
1.173 +choice
1.174 + bool
1.175 + prompt "Maximum log level to see:"
1.176 + default LOG_INFO
1.177 +
1.178 +config LOG_ERROR
1.179 + bool
1.180 + prompt "ERROR"
1.181 + help
1.182 + The build will be silent.
1.183 + Only if there is an error will you see a mesage.
1.184 +
1.185 +config LOG_WARN
1.186 + bool
1.187 + prompt "WARN"
1.188 + help
1.189 + The same as above, plus warnings.
1.190 +
1.191 +config LOG_INFO
1.192 + bool
1.193 + prompt "INFO"
1.194 + help
1.195 + The same as above, plus informational messages (main steps).
1.196 +
1.197 +config LOG_EXTRA
1.198 + bool
1.199 + prompt "EXTRA"
1.200 + help
1.201 + The same as above, plus extra messages (sub-steps).
1.202 +
1.203 +config LOG_DEBUG
1.204 + bool
1.205 + prompt "DEBUG"
1.206 + help
1.207 + The same as above, plus lots of debug information, of which each
1.208 + component's build messages (very noisy!).
1.209 +
1.210 +endchoice
1.211 +
1.212 +config LOG_LEVEL_MAX
1.213 + string
1.214 + default "ERROR" if LOG_ERROR
1.215 + default "WARN" if LOG_WARN
1.216 + default "INFO" if LOG_INFO
1.217 + default "EXTRA" if LOG_EXTRA
1.218 + default "DEBUG" if LOG_DEBUG
1.219 +
1.220 +config LOG_PROGRESS_BAR
1.221 + bool
1.222 + prompt "Progress bar"
1.223 + default n
1.224 + depends on ! LOG_DEBUG
1.225 + help
1.226 + This option will print a "rotating bar" (/-\|) below the last log line
1.227 + to show work is not stalled.
1.228 +
1.229 + Available when not in DEBUG log level.
1.230 +
1.231 +config LOG_USE_COLORS
1.232 + bool
1.233 + prompt "Use colors for logging to console"
1.234 + default n
1.235 + help
1.236 + Use colors to highlight important messages.
1.237 + ERROR: bright red
1.238 + WARN : bright yellow
1.239 + INFO : bright green
1.240 + EXTRA: dim green
1.241 + DEBUG: dim white
1.242 +
1.243 +config LOG_TO_FILE
1.244 + bool
1.245 + prompt "Log to a file"
1.246 + default y
1.247 + help
1.248 + Save *full* logs to a file. Even log levels you didn't specify above
1.249 + will be available in this file.
1.250 +
1.251 +config LOG_FILE
1.252 + string
1.253 + prompt "Log file"
1.254 + default "${CT_PREFIX_DIR}/${CT_TARGET}.log"
1.255 + depends on LOG_TO_FILE
1.256 + help
1.257 + File name into which to put logs.
1.258 +
1.259 +endmenu