config/global.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Mon Apr 23 20:30:34 2007 +0000 (2007-04-23)
changeset 47 7e2539937b6e
parent 41 fd6ad5721f77
child 61 1207acb66003
permissions -rw-r--r--
Second shot at merging from the MIPS branch:
- log level boost for warnings and errors
- option re-ordering
- help updating
yann@1
     1
# Overall toolchain configuration: paths, jobs, etc...
yann@1
     2
yann@1
     3
menu "Paths and misc options"
yann@1
     4
yann@41
     5
config EXPERIMENTAL
yann@41
     6
    bool
yann@41
     7
    prompt "Try features marked as EXPERIMENTAL"
yann@41
     8
    default n
yann@41
     9
    help
yann@41
    10
      If you set this to Y, then you will be able to try very experimental
yann@41
    11
      features.
yann@41
    12
      
yann@41
    13
      Experimental features can be one of:
yann@41
    14
        - working, in which case you should tell me it is!
yann@41
    15
        - buggy, in which case you could try patching and send me the result
yann@41
    16
        - unfinished, in which case you could try hacking it and send me the result
yann@41
    17
        - non-existant, in which case you could also try hacking it in and send the result
yann@41
    18
yann@1
    19
config PARALLEL_JOBS
yann@1
    20
    int
yann@1
    21
    prompt "Number of parallel jobs"
yann@1
    22
    default 1
yann@1
    23
    help
yann@1
    24
      Number of jobs make will be allowed to run concurently.
yann@1
    25
      Set this higher than the number of processors you have, but not too high.
yann@1
    26
      A good rule of thumb is twice the number of processors you have.
yann@1
    27
      
yann@1
    28
      Enter 1 (or 0) to have only one job at a time.
yann@1
    29
yann@1
    30
config LOAD
yann@1
    31
    int
yann@1
    32
    prompt "Maximum allowed load"
yann@1
    33
    default 0
yann@1
    34
    help
yann@1
    35
      Specifies that no new jobs should be started if there are others jobs
yann@1
    36
      running and the load average is at least this value.
yann@1
    37
      
yann@1
    38
      Makes sense on SMP machines only.
yann@1
    39
      
yann@1
    40
      Enter 0 to have no limit on the load average.
yann@1
    41
      
yann@1
    42
      Note: only the integer part of the load is allowed here (you can't enter
yann@1
    43
            0.75 for example).
yann@1
    44
yann@1
    45
config NICE
yann@1
    46
    int
yann@1
    47
    prompt "Nice level"
yann@1
    48
    default 0
yann@1
    49
    range 0 19
yann@1
    50
    help
yann@1
    51
      Renices the build process up.
yann@1
    52
yann@1
    53
config USE_PIPES
yann@1
    54
    bool
yann@1
    55
    prompt "Use -pipe"
yann@1
    56
    default y
yann@1
    57
    help
yann@1
    58
      Use gcc's option -pipe to use pipes rather than temp files when building
yann@1
    59
      the toolchain.
yann@1
    60
yann@1
    61
comment "Paths"
yann@1
    62
yann@1
    63
config TARBALLS_DIR
yann@1
    64
    string
yann@1
    65
    prompt "Tarballs directory"
yann@31
    66
    default "${CT_TOP_DIR}/build/tarballs"
yann@1
    67
    help
yann@1
    68
      This is the directory into which tarballs are going to be stored once
yann@1
    69
      they are downloaded (or otherwise retrieved).
yann@1
    70
yann@1
    71
config SRC_DIR
yann@1
    72
    string
yann@1
    73
    prompt "Extract directory"
yann@31
    74
    default "${CT_TOP_DIR}/build/${CT_TARGET}/${CT_CC}-${CT_CC_VERSION}-${CT_LIBC}-${CT_LIBC_VERSION}/src"
yann@1
    75
    help
yann@1
    76
      This is the directory into which tarballs will be extracted.
yann@1
    77
      
yann@1
    78
      If you will build multiple toolchains, you should arrange to have one
yann@1
    79
      SRC_DIR for each toolchain, as different targets may require different
yann@1
    80
      patches to be applied.
yann@1
    81
yann@31
    82
      You should not need to change this from the default.
yann@31
    83
yann@1
    84
config BUILD_DIR
yann@1
    85
    string
yann@1
    86
    prompt "Build directory"
yann@31
    87
    default "${CT_TOP_DIR}/build/${CT_TARGET}/${CT_CC}-${CT_CC_VERSION}-${CT_LIBC}-${CT_LIBC_VERSION}/build"
yann@1
    88
    help
yann@1
    89
      This is the directory into which builds will occur.
yann@1
    90
      
yann@1
    91
      Once again, arrange for one build directory for each toolchain you build,
yann@1
    92
      to avoid collision.
yann@1
    93
yann@31
    94
      You should not need to change this from the default.
yann@31
    95
yann@1
    96
config PREFIX_DIR
yann@1
    97
    string
yann@1
    98
    prompt "Prefix directory"
yann@1
    99
    default "${HOME}/${CT_TARGET}"
yann@1
   100
    help
yann@1
   101
      This is the path the toolchain will run from.
yann@1
   102
yann@1
   103
config INSTALL_DIR
yann@1
   104
    string
yann@1
   105
#    prompt "Install directory"
yann@1
   106
    default "${CT_PREFIX_DIR}"
yann@1
   107
#    help
yann@1
   108
#      This is the path the target will be installed into.
yann@1
   109
#      
yann@1
   110
#      Normally, you would set this to ${CT_PREFIX_DIR}, but if for some reasons
yann@1
   111
#      you can't write there, you can install somewhere else and have a third
yann@1
   112
#      person do the install for you.
yann@1
   113
#      The reason you might also want to install elsewhere is if you are going
yann@1
   114
#      to package your shinny new toolchain for distribution.
yann@1
   115
yann@1
   116
config CUSTOM_PATCH
yann@1
   117
    bool
yann@1
   118
    prompt "Use custom patch directory"
yann@1
   119
    default n
yann@1
   120
    help
yann@1
   121
      If you have custom patches that you want to be applied, say 'Y' here and
yann@1
   122
      enter the path directory below.
yann@1
   123
      
yann@1
   124
      Note that you must ensure that the patch directory is arranged the same
yann@1
   125
      way the official directory is.
yann@1
   126
yann@1
   127
config CUSTOM_PATCH_ONLY
yann@1
   128
    bool
yann@1
   129
    prompt "Only use custom patches"
yann@1
   130
    default n
yann@1
   131
    depends on CUSTOM_PATCH
yann@1
   132
    help
yann@1
   133
      Don't apply patches coming with CT-NG, only those patches available in
yann@1
   134
      the directory below.
yann@1
   135
      
yann@1
   136
      If you say 'N' here, then the patches provided with CT-NG will be applied
yann@1
   137
      first, and then your patches.
yann@1
   138
yann@1
   139
config CUSTOM_PATCH_DIR
yann@1
   140
    string
yann@1
   141
    prompt "Custom patch directory"
yann@1
   142
    default ""
yann@1
   143
    depends on CUSTOM_PATCH
yann@1
   144
    help
yann@1
   145
      Enter the custom patch directory here.
yann@1
   146
yann@14
   147
config REMOVE_DOCS
yann@14
   148
    bool
yann@14
   149
    prompt "Remove documentation"
yann@14
   150
    default n
yann@14
   151
    help
yann@14
   152
      Remove the installed documentation (man and info pages).
yann@14
   153
      Gains around 8MiB for a uClibc-based, C and C++ compiler.
yann@14
   154
yann@1
   155
comment "Downloading and extracting"
yann@1
   156
yann@1
   157
config NO_DOWNLOAD
yann@1
   158
    bool
yann@1
   159
    prompt "Avoid downloads"
yann@1
   160
    default n
yann@1
   161
    help
yann@1
   162
      Avoid downloading anything. Bail out if a tarball is missing.
yann@1
   163
yann@1
   164
config ONLY_DOWNLOAD
yann@1
   165
    bool
yann@1
   166
    prompt "Only download tarballs"
yann@1
   167
    default n
yann@1
   168
    depends on ! NO_DOWNLOAD
yann@1
   169
    help
yann@1
   170
      Only download the tarballs. Exit once it done.
yann@1
   171
      
yann@1
   172
      Usefull to pre-retrieve the tarballs before going off-line.
yann@1
   173
yann@1
   174
config FORCE_DOWNLOAD
yann@1
   175
    bool
yann@1
   176
    prompt "Force downloads"
yann@1
   177
    default n
yann@1
   178
    depends on ! NO_DOWNLOAD
yann@1
   179
    help
yann@1
   180
      Force downloading tarballs, even if one already exists.
yann@1
   181
      Usefull if you suspect a tarball to be damaged.
yann@1
   182
yann@1
   183
config FORCE_EXTRACT
yann@1
   184
    bool
yann@1
   185
    prompt "Force extractions"
yann@1
   186
    depends on ! ONLY_DOWNLOAD
yann@1
   187
    default n
yann@1
   188
    help
yann@1
   189
      Force extraction of already exctracted tarballs.
yann@1
   190
      
yann@1
   191
      Usefull if you suspect a previous extract did not complete (eg. broken
yann@1
   192
      tarball), or you added a new set of patches for this component.
yann@1
   193
yann@1
   194
comment "Logging"
yann@1
   195
yann@1
   196
choice
yann@1
   197
    bool
yann@1
   198
    prompt "Maximum log level to see:"
yann@1
   199
    default LOG_INFO
yann@1
   200
yann@1
   201
config LOG_ERROR
yann@1
   202
    bool
yann@1
   203
    prompt "ERROR"
yann@1
   204
    help
yann@1
   205
      The build will be silent.
yann@1
   206
      Only if there is an error will you see a mesage.
yann@1
   207
yann@1
   208
config LOG_WARN
yann@1
   209
    bool
yann@1
   210
    prompt "WARN"
yann@1
   211
    help
yann@1
   212
      The same as above, plus warnings.
yann@1
   213
yann@1
   214
config LOG_INFO
yann@1
   215
    bool
yann@1
   216
    prompt "INFO"
yann@1
   217
    help
yann@1
   218
      The same as above, plus informational messages (main steps).
yann@1
   219
yann@1
   220
config LOG_EXTRA
yann@1
   221
    bool
yann@1
   222
    prompt "EXTRA"
yann@1
   223
    help
yann@1
   224
      The same as above, plus extra messages (sub-steps).
yann@1
   225
yann@1
   226
config LOG_DEBUG
yann@1
   227
    bool
yann@1
   228
    prompt "DEBUG"
yann@1
   229
    help
yann@1
   230
      The same as above, plus lots of debug information, of which each
yann@1
   231
      component's build messages (very noisy!).
yann@1
   232
yann@1
   233
endchoice
yann@1
   234
yann@1
   235
config LOG_LEVEL_MAX
yann@1
   236
    string
yann@1
   237
    default "ERROR"   if LOG_ERROR
yann@1
   238
    default "WARN"    if LOG_WARN
yann@1
   239
    default "INFO"    if LOG_INFO
yann@1
   240
    default "EXTRA"   if LOG_EXTRA
yann@1
   241
    default "DEBUG"   if LOG_DEBUG
yann@1
   242
yann@47
   243
config LOG_SEE_TOOLS_WARN
yann@47
   244
    bool
yann@47
   245
    prompt "See warnings from the tool builds"
yann@47
   246
    default n
yann@47
   247
    depends on ! LOG_ERROR
yann@47
   248
    help
yann@47
   249
      If you say Y here, then you will have see the warning lines from
yann@47
   250
      the components builds.
yann@47
   251
yann@47
   252
      It should suffice to say N here, as those will anyway be visible
yann@47
   253
      in the log file (if you want one).
yann@47
   254
yann@1
   255
config LOG_PROGRESS_BAR
yann@1
   256
    bool
yann@1
   257
    prompt "Progress bar"
yann@1
   258
    default n
yann@1
   259
    depends on ! LOG_DEBUG
yann@1
   260
    help
yann@1
   261
      This option will print a "rotating bar" (/-\|) below the last log line
yann@1
   262
      to show work is not stalled.
yann@1
   263
      
yann@1
   264
      Available when not in DEBUG log level.
yann@1
   265
yann@1
   266
config LOG_USE_COLORS
yann@1
   267
    bool
yann@1
   268
    prompt "Use colors for logging to console"
yann@1
   269
    default n
yann@1
   270
    help
yann@1
   271
      Use colors to highlight important messages.
yann@1
   272
      ERROR: bright red
yann@1
   273
      WARN : bright yellow
yann@1
   274
      INFO : bright green
yann@1
   275
      EXTRA: dim green
yann@1
   276
      DEBUG: dim white
yann@1
   277
yann@1
   278
config LOG_TO_FILE
yann@1
   279
    bool
yann@1
   280
    prompt "Log to a file"
yann@1
   281
    default y
yann@1
   282
    help
yann@1
   283
      Save *full* logs to a file. Even log levels you didn't specify above
yann@1
   284
      will be available in this file.
yann@1
   285
yann@47
   286
      As a bonus, there is a script in tools/extractConfig.sh that is able
yann@47
   287
      to extract the configuration of crosstool-NG from the log file.
yann@47
   288
yann@47
   289
      Definitely, say Y.
yann@47
   290
yann@1
   291
config LOG_FILE
yann@1
   292
    string
yann@1
   293
    prompt "Log file"
yann@1
   294
    default "${CT_PREFIX_DIR}/${CT_TARGET}.log"
yann@1
   295
    depends on LOG_TO_FILE
yann@1
   296
    help
yann@1
   297
      File name into which to put logs.
yann@1
   298
yann@1
   299
endmenu