Hop, a somewhat more efficient progress bar, less CPU consuming, if that was a problem :-)
(a litlle recreation while toochains are building...)
1.1 --- a/scripts/crosstool.sh Tue May 08 20:24:26 2007 +0000
1.2 +++ b/scripts/crosstool.sh Tue May 08 20:41:08 2007 +0000
1.3 @@ -45,12 +45,13 @@
1.4 printf "[%02d:%02d]" $((elapsed/60)) $((elapsed%60))
1.5 }
1.6 _CT_PROG_BAR() {
1.7 - [ $((cpt/10)) -eq 0 ] && echo -en "\r`_CT_PROG_BAR_DATE` /"
1.8 - [ $((cpt/10)) -eq 1 ] && echo -en "\r`_CT_PROG_BAR_DATE` -"
1.9 - [ $((cpt/10)) -eq 2 ] && echo -en "\r`_CT_PROG_BAR_DATE` \\"
1.10 - [ $((cpt/10)) -eq 3 ] && echo -en "\r`_CT_PROG_BAR_DATE` |"
1.11 - cpt=$(((cpt+1)%40))
1.12 + [ ${CT_PROG_BAR_CPT} -eq 0 ] && echo -en "\r`_CT_PROG_BAR_DATE` /"
1.13 + [ ${CT_PROG_BAR_CPT} -eq 10 ] && echo -en "\r`_CT_PROG_BAR_DATE` -"
1.14 + [ ${CT_PROG_BAR_CPT} -eq 20 ] && echo -en "\r`_CT_PROG_BAR_DATE` \\"
1.15 + [ ${CT_PROG_BAR_CPT} -eq 30 ] && echo -en "\r`_CT_PROG_BAR_DATE` |"
1.16 + CT_PROG_BAR_CPT=$(((CT_PROG_BAR_CPT+1)%40))
1.17 }
1.18 + CT_PROG_BAR_CPT=0
1.19 CT_PROG_BAR=_CT_PROG_BAR
1.20 export -f _CT_PROG_BAR
1.21 else
2.1 --- a/scripts/functions Tue May 08 20:24:26 2007 +0000
2.2 +++ b/scripts/functions Tue May 08 20:41:08 2007 +0000
2.3 @@ -91,6 +91,7 @@
2.4 normal="CT_NORMAL_COLOR"
2.5 if [ ${cur_l} -le ${max_level} ]; then
2.6 echo -e "\r${!color}${l}${!normal}"
2.7 + CT_PROG_BAR_CPT=0 # Force redrawing progress bar on next 'unlogged' line
2.8 else
2.9 ${CT_PROG_BAR}
2.10 fi