scripts/build/arch/microblaze.sh
author "Yann E. MORIN" <yann.morin.1998@free.fr>
Thu Dec 27 12:45:22 2012 +0100 (2012-12-27)
changeset 3152 b286c7993be5
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>
david@3053
     1
# Compute microblaze specific values
david@3053
     2
david@3053
     3
CT_DoArchTupleValues () {
david@3053
     4
    # The architecture part of the tuple:
david@3053
     5
    CT_TARGET_ARCH="${CT_ARCH}${target_endian_el}"
david@3053
     6
david@3053
     7
    # gcc ./configure flags
david@3053
     8
    CT_ARCH_WITH_ARCH=
david@3053
     9
    CT_ARCH_WITH_ABI=
david@3053
    10
    CT_ARCH_WITH_CPU=
david@3053
    11
    CT_ARCH_WITH_TUNE=
david@3053
    12
    CT_ARCH_WITH_FPU=
david@3053
    13
    CT_ARCH_WITH_FLOAT=
david@3053
    14
david@3053
    15
    # CFLAGS
david@3053
    16
    case "${CT_ARCH_FLOAT_HW},${CT_ARCH_FLOAT_SW}" in
david@3053
    17
        y,) CT_ARCH_FLOAT_CFLAG="-mhard-float" ;;
david@3053
    18
        ,y) CT_ARCH_FLOAT_CFLAG="-msoft-float" ;;
david@3053
    19
    esac
david@3053
    20
david@3053
    21
}