1 # Options specific to logging
7 prompt "Maximum log level to see:"
8 default LOG_INFO if !DEBUG_CT
9 default LOG_DEBUG if DEBUG_CT
15 The build will be silent.
16 Only if there is an error will you see a message.
22 The same as above, plus warnings.
28 The same as above, plus informational messages (main steps).
34 The same as above, plus extra messages (sub-steps).
40 The same as above, plus all components build messages (very noisy!).
46 The same as above, plus lots of crosstool-NG debug information.
52 default "ERROR" if LOG_ERROR
53 default "WARN" if LOG_WARN
54 default "INFO" if LOG_INFO
55 default "EXTRA" if LOG_EXTRA
56 default "ALL" if LOG_ALL
57 default "DEBUG" if LOG_DEBUG
59 config LOG_SEE_TOOLS_WARN
61 prompt "Warnings from the tools' builds"
62 depends on ! LOG_ERROR
64 Treat warnings from the different tools as crosstool-NG warnings.
65 If you say 'y' here, then those warnings will be prefixed with
66 '[WARN ]' instead of the default '[ALL ]'.
68 You can safely say 'n' here. Those warnings will anyway be
69 recorded in the log file (provided you configured one).
71 Tools error will always be logged as crosstool-NG errors.
73 config LOG_PROGRESS_BAR
77 depends on ! LOG_ALL && ! LOG_DEBUG
79 If you say 'y' here, you'll be able to see the elapsed time.
81 As a bonus, you'll also get a rotating bar (/-\|) showing you
82 that the build is not stalled (the bar rotates 1/4 every 10 lines
83 of components build log).
85 Note that the elapsed time can stall for a little while if a
86 component has long commands, as the elapsed time is only updated
91 prompt "Log to a file"
94 Save *full* logs to a file. Even log levels you didn't specify above
95 will be available in this file. The log file will be named build.log
96 and stored in the toolchain prefix dir (set above).
100 config LOG_FILE_COMPRESS
102 prompt "Compress the log file"
104 depends on LOG_TO_FILE
106 Compress the log file once the toolchain is successfully built.