scripts/build/debug.sh
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Sun May 20 13:48:26 2007 +0000 (2007-05-20)
changeset 112 ea15433daba0
child 182 223c84ec2d90
permissions -rw-r--r--
Ah! I finally have a progress bar that doesn't stall the build!
- pipe size in Linux is only 8*512=4096 bytes
- pipe size is not setable
- when the feeding process spits out data faster than the eating
process can read it, then the feeding process stalls after 4KiB
of data sent to the pipe
- for us, the progress bar would spawn a sub-shell every line,
and the sub-shell would in turn spawn a 'date' command.
Which was sloooww as hell, and would cause some kind of a
starvation: the pipe was full most of the time, and the
feeding process was stalled all this time.

Now, we use internal variables and a little hack based onan offset
to determine the elapsed time. Much faster this way, but still
CPU-intensive.
     1 # Wrapper to build the debug facilities
     2 
     3 # List all debug facilities, and parse their scripts
     4 CT_DEBUG_FACILITY_LIST=
     5 for f in "${CT_TOP_DIR}/scripts/build/debug/"*.sh; do
     6     is_enabled=
     7     . "${f}"
     8     f=`basename "${f}" .sh`
     9     if [ "${is_enabled}" = "y" ]; then
    10         CT_DEBUG_FACILITY_LIST="${CT_DEBUG_FACILITY_LIST} ${f}"
    11     fi
    12 done
    13 
    14 # Download the debug facilities
    15 do_debug_get() {
    16     for f in ${CT_DEBUG_FACILITY_LIST}; do
    17         do_debug_${f}_get
    18     done
    19 }
    20 
    21 # Extract and patch the debug facilities
    22 do_debug_extract() {
    23     for f in ${CT_DEBUG_FACILITY_LIST}; do
    24         do_debug_${f}_extract
    25     done
    26 }
    27 
    28 # Build the debug facilities
    29 do_debug() {
    30     for f in ${CT_DEBUG_FACILITY_LIST}; do
    31         do_debug_${f}_build
    32     done
    33 }
    34