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>
1 # This will build and install sstrip to run on host and sstrip target files
4 do_sstrip_extract() { :; }
7 if [ "${CT_SSTRIP}" = "y" ]; then
9 CT_GetFile sstrip .c http://git.buildroot.net/buildroot/plain/toolchain/sstrip
13 # We leave the sstrip maintenance to the buildroot people:
14 # -> any fix-up goes directly there
15 # -> we don't have patches for it
16 # -> we don't need to patch it
17 # -> just create a directory in src/, and copy it there.
18 CT_DoExecLog DEBUG mkdir -p "${CT_SRC_DIR}/sstrip"
19 CT_DoExecLog DEBUG cp -v "${CT_TARBALLS_DIR}/sstrip.c" "${CT_SRC_DIR}/sstrip"
23 CT_DoStep INFO "Installing sstrip"
24 mkdir -p "${CT_BUILD_DIR}/build-sstrip"
25 cd "${CT_BUILD_DIR}/build-sstrip"
27 CT_DoLog EXTRA "Building sstrip"
28 CT_DoExecLog ALL "${CT_HOST}-gcc" -Wall -o sstrip "${CT_SRC_DIR}/sstrip/sstrip.c"
30 CT_DoLog EXTRA "Installing sstrip"
31 CT_DoExecLog ALL install -m 755 sstrip "${CT_PREFIX_DIR}/bin/${CT_TARGET}-sstrip"