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 ARM-specific values
3 CT_DoArchTupleValues() {
4 # The architecture part of the tuple:
5 CT_TARGET_ARCH="${CT_ARCH}${target_endian_eb}"
7 # The system part of the tuple:
8 case "${CT_LIBC},${CT_ARCH_ARM_EABI}" in
9 *glibc,y) CT_TARGET_SYS=gnueabi;;
10 uClibc,y) CT_TARGET_SYS=uclibcgnueabi;;
11 *,y) CT_TARGET_SYS=eabi;;
14 # Set the default instruction set mode
15 case "${CT_ARCH_ARM_MODE}" in
18 CT_ARCH_CC_CORE_EXTRA_CONFIG="--with-mode=thumb"
19 CT_ARCH_CC_EXTRA_CONFIG="--with-mode=thumb"
20 # CT_ARCH_TARGET_CFLAGS="-mthumb"
24 if [ "${CT_ARCH_ARM_INTERWORKING}" = "y" ]; then
25 CT_ARCH_TARGET_CFLAGS+=" -mthumb-interwork"