config/logging.in
changeset 446 d205527c5e01
parent 445 17aa08b441f2
child 447 db8bd468b0c0
     1.1 --- a/config/logging.in	Thu Apr 17 20:02:07 2008 +0000
     1.2 +++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.3 @@ -1,110 +0,0 @@
     1.4 -# Options specific to logging
     1.5 -
     1.6 -comment "Logging"
     1.7 -
     1.8 -choice
     1.9 -    bool
    1.10 -    prompt "Maximum log level to see:"
    1.11 -    default LOG_INFO if !DEBUG_CT
    1.12 -    default LOG_DEBUG if DEBUG_CT
    1.13 -
    1.14 -config LOG_ERROR
    1.15 -    bool
    1.16 -    prompt "ERROR"
    1.17 -    help
    1.18 -      The build will be silent.
    1.19 -      Only if there is an error will you see a message.
    1.20 -
    1.21 -config LOG_WARN
    1.22 -    bool
    1.23 -    prompt "WARN"
    1.24 -    help
    1.25 -      The same as above, plus warnings.
    1.26 -
    1.27 -config LOG_INFO
    1.28 -    bool
    1.29 -    prompt "INFO"
    1.30 -    help
    1.31 -      The same as above, plus informational messages (main steps).
    1.32 -
    1.33 -config LOG_EXTRA
    1.34 -    bool
    1.35 -    prompt "EXTRA"
    1.36 -    help
    1.37 -      The same as above, plus extra messages (sub-steps).
    1.38 -
    1.39 -config LOG_DEBUG
    1.40 -    bool
    1.41 -    prompt "DEBUG"
    1.42 -    help
    1.43 -      The same as above, plus lots of crosstool-NG debug information.
    1.44 -
    1.45 -config LOG_ALL
    1.46 -    bool
    1.47 -    prompt "ALL"
    1.48 -    help
    1.49 -      The same as above, plus all components build messages (very noisy!).
    1.50 -
    1.51 -endchoice
    1.52 -
    1.53 -config LOG_LEVEL_MAX
    1.54 -    string
    1.55 -    default "ERROR"   if LOG_ERROR
    1.56 -    default "WARN"    if LOG_WARN
    1.57 -    default "INFO"    if LOG_INFO
    1.58 -    default "EXTRA"   if LOG_EXTRA
    1.59 -    default "DEBUG"   if LOG_DEBUG
    1.60 -    default "ALL"     if LOG_ALL
    1.61 -
    1.62 -config LOG_SEE_TOOLS_WARN
    1.63 -    bool
    1.64 -    prompt "Warnings from the tools' builds"
    1.65 -    default n
    1.66 -    depends on ! LOG_ERROR
    1.67 -    help
    1.68 -      Treat warnings from the different tools as crosstool-NG warnings.
    1.69 -      If you say 'y' here, then those warnings will be prefixed with
    1.70 -      '[WARN ]' instead of the default '[ALL  ]'.
    1.71 -
    1.72 -      You can safely say 'n' here. Those warnings will anyway be
    1.73 -      recorded in the log file (provided you configured one).
    1.74 -
    1.75 -      Tools error will always be logged as crosstool-NG errors.
    1.76 -
    1.77 -config LOG_PROGRESS_BAR
    1.78 -    bool
    1.79 -    prompt "Progress bar"
    1.80 -    default y
    1.81 -    depends on ! LOG_ALL
    1.82 -    help
    1.83 -      If you say 'y' here, you'll be able to see the elapsed time.
    1.84 -      
    1.85 -      As a bonus, you'll also get a rotating bar (/-\|) showing you
    1.86 -      that the build is not stalled (the bar rotates 1/4 every 10 lines
    1.87 -      of components build log).
    1.88 -
    1.89 -      Note that the elapsed time can stall for a little while if a
    1.90 -      component has long commands, as the elapsed time is only updated
    1.91 -      each line.
    1.92 -
    1.93 -config LOG_TO_FILE
    1.94 -    bool
    1.95 -    prompt "Log to a file"
    1.96 -    default y
    1.97 -    help
    1.98 -      Save *full* logs to a file. Even log levels you didn't specify above
    1.99 -      will be available in this file. The log file will be named build.log
   1.100 -      and stored in the toolchain prefix dir (set above).
   1.101 -
   1.102 -      As a bonus, there is a script in tools/extractConfig.sh that is able
   1.103 -      to extract the configuration of crosstool-NG from the log file.
   1.104 -
   1.105 -      Definitely, say Y.
   1.106 -
   1.107 -config LOG_FILE_COMPRESS
   1.108 -    bool
   1.109 -    prompt "Compress the log file"
   1.110 -    default n
   1.111 -    depends on LOG_TO_FILE
   1.112 -    help
   1.113 -      Compress the log file once the toolchain is successfully built.