Use ${CT_TOP_DIR}/build as a base for build directories (used in default values for paths).
Remove this directory on distclean (hard-coded).
Mark the version to be 0.0.1-svn (no release yet).
1 # Overall toolchain configuration: paths, jobs, etc...
3 menu "Paths and misc options"
7 prompt "Number of parallel jobs"
10 Number of jobs make will be allowed to run concurently.
11 Set this higher than the number of processors you have, but not too high.
12 A good rule of thumb is twice the number of processors you have.
14 Enter 1 (or 0) to have only one job at a time.
18 prompt "Maximum allowed load"
21 Specifies that no new jobs should be started if there are others jobs
22 running and the load average is at least this value.
24 Makes sense on SMP machines only.
26 Enter 0 to have no limit on the load average.
28 Note: only the integer part of the load is allowed here (you can't enter
37 Renices the build process up.
44 Use gcc's option -pipe to use pipes rather than temp files when building
51 prompt "Tarballs directory"
52 default "${CT_TOP_DIR}/build/tarballs"
54 This is the directory into which tarballs are going to be stored once
55 they are downloaded (or otherwise retrieved).
59 prompt "Extract directory"
60 default "${CT_TOP_DIR}/build/${CT_TARGET}/${CT_CC}-${CT_CC_VERSION}-${CT_LIBC}-${CT_LIBC_VERSION}/src"
62 This is the directory into which tarballs will be extracted.
64 If you will build multiple toolchains, you should arrange to have one
65 SRC_DIR for each toolchain, as different targets may require different
66 patches to be applied.
68 You should not need to change this from the default.
72 prompt "Build directory"
73 default "${CT_TOP_DIR}/build/${CT_TARGET}/${CT_CC}-${CT_CC_VERSION}-${CT_LIBC}-${CT_LIBC_VERSION}/build"
75 This is the directory into which builds will occur.
77 Once again, arrange for one build directory for each toolchain you build,
80 You should not need to change this from the default.
84 prompt "Prefix directory"
85 default "${HOME}/${CT_TARGET}"
87 This is the path the toolchain will run from.
91 # prompt "Install directory"
92 default "${CT_PREFIX_DIR}"
94 # This is the path the target will be installed into.
96 # Normally, you would set this to ${CT_PREFIX_DIR}, but if for some reasons
97 # you can't write there, you can install somewhere else and have a third
98 # person do the install for you.
99 # The reason you might also want to install elsewhere is if you are going
100 # to package your shinny new toolchain for distribution.
104 prompt "Use custom patch directory"
107 If you have custom patches that you want to be applied, say 'Y' here and
108 enter the path directory below.
110 Note that you must ensure that the patch directory is arranged the same
111 way the official directory is.
113 config CUSTOM_PATCH_ONLY
115 prompt "Only use custom patches"
117 depends on CUSTOM_PATCH
119 Don't apply patches coming with CT-NG, only those patches available in
122 If you say 'N' here, then the patches provided with CT-NG will be applied
123 first, and then your patches.
125 config CUSTOM_PATCH_DIR
127 prompt "Custom patch directory"
129 depends on CUSTOM_PATCH
131 Enter the custom patch directory here.
135 prompt "Remove documentation"
138 Remove the installed documentation (man and info pages).
139 Gains around 8MiB for a uClibc-based, C and C++ compiler.
141 comment "Downloading and extracting"
145 prompt "Avoid downloads"
148 Avoid downloading anything. Bail out if a tarball is missing.
152 prompt "Only download tarballs"
154 depends on ! NO_DOWNLOAD
156 Only download the tarballs. Exit once it done.
158 Usefull to pre-retrieve the tarballs before going off-line.
160 config FORCE_DOWNLOAD
162 prompt "Force downloads"
164 depends on ! NO_DOWNLOAD
166 Force downloading tarballs, even if one already exists.
167 Usefull if you suspect a tarball to be damaged.
171 prompt "Force extractions"
172 depends on ! ONLY_DOWNLOAD
175 Force extraction of already exctracted tarballs.
177 Usefull if you suspect a previous extract did not complete (eg. broken
178 tarball), or you added a new set of patches for this component.
184 prompt "Maximum log level to see:"
191 The build will be silent.
192 Only if there is an error will you see a mesage.
198 The same as above, plus warnings.
204 The same as above, plus informational messages (main steps).
210 The same as above, plus extra messages (sub-steps).
216 The same as above, plus lots of debug information, of which each
217 component's build messages (very noisy!).
223 default "ERROR" if LOG_ERROR
224 default "WARN" if LOG_WARN
225 default "INFO" if LOG_INFO
226 default "EXTRA" if LOG_EXTRA
227 default "DEBUG" if LOG_DEBUG
229 config LOG_PROGRESS_BAR
231 prompt "Progress bar"
233 depends on ! LOG_DEBUG
235 This option will print a "rotating bar" (/-\|) below the last log line
236 to show work is not stalled.
238 Available when not in DEBUG log level.
240 config LOG_USE_COLORS
242 prompt "Use colors for logging to console"
245 Use colors to highlight important messages.
254 prompt "Log to a file"
257 Save *full* logs to a file. Even log levels you didn't specify above
258 will be available in this file.
263 default "${CT_PREFIX_DIR}/${CT_TARGET}.log"
264 depends on LOG_TO_FILE
266 File name into which to put logs.