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 # ARM specific configuration file
5 default "arm" if ARCH_ARM_MODE_ARM
6 default "thumb" if ARCH_ARM_MODE_THUMB
10 prompt "Default instruction set mode"
11 default ARCH_ARM_MODE_ARM
13 config ARCH_ARM_MODE_ARM
17 Defaults to emitting instructions in the ARM mode.
19 config ARCH_ARM_MODE_THUMB
23 Defaults to emitting instructions in the THUMB mode.
27 config ARCH_ARM_INTERWORKING
29 prompt "Use Thumb-interworking (READ HELP)"
31 Excerpt from the gcc manual:
33 > Generate code which supports calling between the ARM and Thumb
34 > instruction sets. Without this option the two instruction sets
35 > cannot be reliably used inside one program. The default is
36 > [not to use interwork], since slightly larger code is generated
37 > when [interwork] is specified.
39 NOTE: Interworking in crosstool-NG is not sell-tested. Use at your
40 own risks, and report success and/or failure.
47 Set up the toolchain so that it generates EABI-compliant binaries.
49 config ARCH_ARM_ABI_OK
52 depends on ! ARCH_ARM_EABI
53 select ARCH_SUPPORTS_WITH_ABI