summaryrefslogtreecommitdiff
path: root/scripts/functions
diff options
context:
space:
mode:
authorJavier Viguera <javier.viguera@digi.com>2011-04-07 09:52:23 (GMT)
committerJavier Viguera <javier.viguera@digi.com>2011-04-07 09:52:23 (GMT)
commit98ceb8faf3d8308688bbb52c268753b35ed96887 (patch)
tree30b59c59919b9f7b813a96c87dafafc4a7446db3 /scripts/functions
parent5e27ad1e5aabdbc0633c380c4ab2959b34a55134 (diff)
functions: avoid CR when progress bar is not enabled
Using CT-NG with progress bar disabled, still prints CR ('\r') characters on the output. When you capture the output to a file as part of an automated build, it shows extra empty lines. For example: ------------------------------------------------------------ [INFO ] Performing some trivial sanity checks [INFO ] Build started 20110404.113619 [INFO ] Building environment variables [EXTRA] Preparing working directories [EXTRA] Installing user-supplied crosstool-NG configuration ------------------------------------------------------------ Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Diffstat (limited to 'scripts/functions')
-rw-r--r--scripts/functions2
1 files changed, 1 insertions, 1 deletions
diff --git a/scripts/functions b/scripts/functions
index 9f6d0f4..c504684 100644
--- a/scripts/functions
+++ b/scripts/functions
@@ -106,7 +106,7 @@ CT_DoLog() {
printf "[%-5s]%*s%s%s\n" "${cur_L}" "${indent}" " " "${line}"
if [ ${cur_l} -le ${max_level} ]; then
# Only print to console (fd #6) if log level is high enough.
- printf "\r[%-5s]%*s%s%s\n" "${cur_L}" "${indent}" " " "${line}" >&6
+ printf "${CT_LOG_PROGRESS_BAR:+\r}[%-5s]%*s%s%s\n" "${cur_L}" "${indent}" " " "${line}" >&6
fi
if [ "${CT_LOG_PROGRESS_BAR}" = "y" ]; then
printf "\r[%02d:%02d] %s " $((SECONDS/60)) $((SECONDS%60)) "${_prog_bar[$((_prog_bar_cpt/10))]}" >&6