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 # Wrapper to build the test suite facilities
3 # Current assumption: test suites are independent of each other
4 # - no order handling required.
6 # List all test suite facilities, and parse their scripts
7 CT_TEST_SUITE_FACILITY_LIST=
8 for f in "${CT_LIB_DIR}/scripts/build/test_suite/"*.sh; do
9 _f="$(basename "${f}" .sh)"
10 __f="CT_TEST_SUITE_${_f}"
11 __f=`echo ${__f} | tr "[:lower:]" "[:upper:]"`
12 if [ "${!__f}" = "y" ]; then
13 CT_DoLog DEBUG "Enabling test suite '${_f}'"
15 CT_TEST_SUITE_FACILITY_LIST="${CT_TEST_SUITE_FACILITY_LIST} ${_f}"
17 CT_DoLog DEBUG "Disabling test suite '${_f}'"
21 # Download the test suite facilities
23 for f in ${CT_TEST_SUITE_FACILITY_LIST}; do
24 do_test_suite_${f}_get
28 # Extract and patch the test suite facilities
29 do_test_suite_extract() {
30 for f in ${CT_TEST_SUITE_FACILITY_LIST}; do
31 do_test_suite_${f}_extract
35 # Build the test suite facilities
37 for f in ${CT_TEST_SUITE_FACILITY_LIST}; do
38 do_test_suite_${f}_build