scripts/build/arch/sh.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 2760 b402a49734a3
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 sh-specific values
     2 
     3 CT_DoArchTupleValues () {
     4     # The architecture part of the tuple:
     5     CT_TARGET_ARCH="${CT_ARCH_SH_VARIANT}${target_endian_eb}"
     6 
     7     # gcc ./configure flags
     8     CT_ARCH_WITH_ARCH=
     9     CT_ARCH_WITH_ABI=
    10     CT_ARCH_WITH_CPU=
    11     CT_ARCH_WITH_TUNE=
    12     CT_ARCH_WITH_FPU=
    13     CT_ARCH_WITH_FLOAT=
    14 
    15     # Endianness stuff
    16     case "${CT_ARCH_ENDIAN}" in
    17         big)    CT_ARCH_ENDIAN_CFLAG=-mb;;
    18         little) CT_ARCH_ENDIAN_CFLAG=-ml;;
    19     esac
    20 
    21     # CFLAGS
    22     case "${CT_ARCH_SH_VARIANT}" in
    23         sh3)    CT_ARCH_ARCH_CFLAG=-m3;;
    24         sh4*)
    25             # softfp is not possible for SuperH, no need to test for it.
    26             case "${CT_ARCH_FLOAT}" in
    27                 hard)
    28                     CT_ARCH_ARCH_CFLAG="-m4${CT_ARCH_SH_VARIANT##sh?}"
    29                     ;;
    30                 soft)
    31                     CT_ARCH_ARCH_CFLAG="-m4${CT_ARCH_SH_VARIANT##sh?}-nofpu"
    32                     ;;
    33             esac
    34             ;;
    35     esac
    36     CT_ARCH_FLOAT_CFLAG=
    37 }