Mercurialcrosstool-ng / file revision
summary | shortlog | changelog | graph | tags | branches | files | changeset | file | latest | revisions | annotate | diff | raw | help
scripts/showTuple.sh.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Fri Aug 19 22:53:48 2011 +0200 (2011-08-19)
changeset 2620 d9c5b3b75864
parent 1336 bc8b9381f637
child 2838 822af73497bf
permissions -rw-r--r--
Makefile: introduce PROG_NAME to contain the 'ct-ng' executable name

With the upcomming --program-{prefix,suffix,transform-name} options,
we'll have a need to centralise the actual executable name, that is
now no longer be a constant.

Rather than spread the prefix/suffix through-out the code, just
centralise the name setting in one place. Beside, transform-name
would not be possible without setting the name at a single location.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr> 
     1 #!@@CT_bash@@

     2 

     3 # What we need:

     4 #  - the .config file

     5 

     6 # Parse the tools' paths configuration

     7 . "${CT_LIB_DIR}/paths.mk"

     8 

     9 # We'll need the stdout later, save it

    10 exec 7>&1

    11 

    12 # Parse the common functions

    13 . "${CT_LIB_DIR}/scripts/functions"

    14 

    15 # Don't care about any log file

    16 exec >/dev/null

    17 rm -f "${tmp_log_file}"

    18 

    19 # Parse the configuration file

    20 . .config.2

    21 

    22 # Parse architecture and kernel specific functions

    23 . "${CT_LIB_DIR}/scripts/build/arch/${CT_ARCH}.sh"

    24 . "${CT_LIB_DIR}/scripts/build/kernel/${CT_KERNEL}.sh"

    25 

    26 # Build CT_TARGET

    27 CT_DoBuildTargetTuple

    28 

    29 # All this for this single echo... :-( Sigh, I'll have to re-arrange things...

    30 echo "${CT_TARGET}" >&7
crosstool-ng