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