scripts: add "FILE" and "CFG" debug levels.
I ran into some minor difficulties looking through the build log for a
particular file: I wasn't interested in seeing it unpacked, but only
when it is built or installed. Adding these two levels allows me to
differentiate between those cases.
[Yann E. MORIN: Those are blind log levels, and are used only to search
in the build-log afterward.]
Signed-off-by: Anthony Foiani <anthony.foiani@gmail.com>
6 # Parse the tools' paths configuration
7 . "${CT_LIB_DIR}/paths.mk"
9 # We'll need the stdout later, save it
12 # Parse the common functions
13 . "${CT_LIB_DIR}/scripts/functions"
15 # Don't care about any log file
17 rm -f "${tmp_log_file}"
19 # Parse the configuration file
22 # Parse architecture and kernel specific functions
23 . "${CT_LIB_DIR}/scripts/build/arch/${CT_ARCH}.sh"
24 . "${CT_LIB_DIR}/scripts/build/kernel/${CT_KERNEL}.sh"
29 # All this for this single echo... :-( Sigh, I'll have to re-arrange things...
30 echo "${CT_TARGET}" >&7