scripts/build/arch/powerpc.sh
author "Yann E. MORIN" <yann.morin.1998@free.fr>
Thu Dec 27 12:45:22 2012 +0100 (2012-12-27)
changeset 3152 b286c7993be5
parent 2675 7c288c777455
child 3169 9d0b37f08a10
permissions -rw-r--r--
scripts/addToolsVersion: properly handle .in vs. .in.2

While most components have their version in the .in file, some
have it in the .in.2 (eg. elf2flt).

Currently, to handle this case, we indiscriminately munge both files,
but this is wrong: in the elf2flt case, if we add a binutils version,
we do not want it to be added to elf2flt, and conversely.

So, for each tool, we need to explicitly know what file to munge.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
     1 # Compute powerpc-specific values
     2 
     3 CT_DoArchTupleValues () {
     4     # The architecture part of the tuple, override only for 64-bit
     5     if [ "${CT_ARCH_64}" = "y" ]; then
     6         CT_TARGET_ARCH="powerpc64"
     7     fi
     8 
     9     # Only override values when ABI is not the default
    10     case "${CT_ARCH_powerpc_ABI}" in
    11         eabi)
    12             # EABI is only for bare-metal, so libc ∈ [none,newlib]
    13             CT_TARGET_SYS="eabi"
    14             ;;
    15         spe)
    16             case "${CT_LIBC}" in
    17                 none|newlib)    CT_TARGET_SYS="spe";;
    18                 *glibc)         CT_TARGET_SYS="gnuspe";;
    19                 uClibc)         CT_TARGET_SYS="uclibcgnuspe";;
    20             esac
    21             ;;
    22     esac
    23 
    24     # Add extra flags for SPE if needed
    25     if [ "${CT_ARCH_powerpc_ABI_SPE}" = "y" ]; then
    26         CT_ARCH_TARGET_CFLAGS="-mabi=spe -mspe"
    27         CT_ARCH_CC_CORE_EXTRA_CONFIG="--enable-e500_double"
    28         CT_ARCH_CC_EXTRA_CONFIG="--enable-e500_double"
    29     fi
    30 }