crosstool-ng/config/global/logging.in
Yann E. MORIN" dd862bd7a4 Move config files around, and clean up the mess in the config/ directory.
config/kernel/kernel_linux.in            |   12     6     6     0 +-
 config/paths.in                          |   89     0    89     0 ----------------
 config/kernel_linux_headers_install.in   |  168     0   168     0 ------------------------------
 config/kernel.in                         |    2     1     1     0
 config/kernel_linux_headers_copy.in      |   42     0    42     0 --------
 config/cc.in                             |    2     1     1     0
 config/logging.in                        |  110     0   110     0 --------------------
 config/build-behave.in                   |   45     0    45     0 --------
 config/libc_uClibc.in                    |  101     0   101     0 ------------------
 config/kernel_linux_headers_sanitised.in |   62     0    62     0 -----------
 config/ct-behave.in                      |   82     0    82     0 ---------------
 config/kernel_linux.in                   |  134     0   134     0 ------------------------
 config/global.in                         |   10     5     5     0 +-
 config/download_extract.in               |  171     0   171     0 -------------------------------
 config/cc_gcc.in                         |  130     0   130     0 ------------------------
 config/libc_glibc.in                     |  124     0   124     0 ----------------------
 config/libc.in                           |    4     2     2     0
 17 files changed, 15 insertions(+), 1273 deletions(-)
2008-04-17 20:26:25 +00:00

111 lines
2.8 KiB
Plaintext

# Options specific to logging
comment "Logging"
choice
bool
prompt "Maximum log level to see:"
default LOG_INFO if !DEBUG_CT
default LOG_DEBUG if DEBUG_CT
config LOG_ERROR
bool
prompt "ERROR"
help
The build will be silent.
Only if there is an error will you see a message.
config LOG_WARN
bool
prompt "WARN"
help
The same as above, plus warnings.
config LOG_INFO
bool
prompt "INFO"
help
The same as above, plus informational messages (main steps).
config LOG_EXTRA
bool
prompt "EXTRA"
help
The same as above, plus extra messages (sub-steps).
config LOG_DEBUG
bool
prompt "DEBUG"
help
The same as above, plus lots of crosstool-NG debug information.
config LOG_ALL
bool
prompt "ALL"
help
The same as above, plus all components build messages (very noisy!).
endchoice
config LOG_LEVEL_MAX
string
default "ERROR" if LOG_ERROR
default "WARN" if LOG_WARN
default "INFO" if LOG_INFO
default "EXTRA" if LOG_EXTRA
default "DEBUG" if LOG_DEBUG
default "ALL" if LOG_ALL
config LOG_SEE_TOOLS_WARN
bool
prompt "Warnings from the tools' builds"
default n
depends on ! LOG_ERROR
help
Treat warnings from the different tools as crosstool-NG warnings.
If you say 'y' here, then those warnings will be prefixed with
'[WARN ]' instead of the default '[ALL ]'.
You can safely say 'n' here. Those warnings will anyway be
recorded in the log file (provided you configured one).
Tools error will always be logged as crosstool-NG errors.
config LOG_PROGRESS_BAR
bool
prompt "Progress bar"
default y
depends on ! LOG_ALL
help
If you say 'y' here, you'll be able to see the elapsed time.
As a bonus, you'll also get a rotating bar (/-\|) showing you
that the build is not stalled (the bar rotates 1/4 every 10 lines
of components build log).
Note that the elapsed time can stall for a little while if a
component has long commands, as the elapsed time is only updated
each line.
config LOG_TO_FILE
bool
prompt "Log to a file"
default y
help
Save *full* logs to a file. Even log levels you didn't specify above
will be available in this file. The log file will be named build.log
and stored in the toolchain prefix dir (set above).
As a bonus, there is a script in tools/extractConfig.sh that is able
to extract the configuration of crosstool-NG from the log file.
Definitely, say Y.
config LOG_FILE_COMPRESS
bool
prompt "Compress the log file"
default n
depends on LOG_TO_FILE
help
Compress the log file once the toolchain is successfully built.