crosstool-ng: scripts/build/companion_tools/400-libtool.sh@9bafe9c8f0b3

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>
(transplanted from cbd07f3dd6e3689a6b971e999aa82d09fb94d515)

     1 # Build script for libtool

     3 CT_LIBTOOL_VERSION=2.2.6b

     5 do_companion_tools_libtool_get() {

     6     CT_GetFile "libtool-${CT_LIBTOOL_VERSION}" \

     7                {ftp,http}://ftp.gnu.org/gnu/libtool

8 }

    10 do_companion_tools_libtool_extract() {

    11     CT_Extract "libtool-${CT_LIBTOOL_VERSION}"

    12     CT_Patch "libtool" "${CT_LIBTOOL_VERSION}"

    13 }

    15 do_companion_tools_libtool_build() {

    16     CT_DoStep EXTRA "Installing libtool"

    17     mkdir -p "${CT_BUILD_DIR}/build-libtool"

    18     CT_Pushd "${CT_BUILD_DIR}/build-libtool"

    20     CT_DoExecLog CFG \

    21     "${CT_SRC_DIR}/libtool-${CT_LIBTOOL_VERSION}/configure" \

    22         --prefix="${CT_TOOLS_OVERIDE_DIR}"

    23     CT_DoExecLog ALL make

    24     CT_DoExecLog ALL make install

    25     CT_Popd

    26     CT_EndStep

    27 }

author	Javier Viguera <javier.viguera@digi.com>
	Thu Apr 07 11:52:23 2011 +0200 (2011-04-07)
branch	1.10
changeset 2398	9bafe9c8f0b3
parent 1901	bdb3a98e064b
child 2309	2e0f0757289d
permissions	-rw-r--r--