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 # Binary utilities menu
3 menu "Binary utilities"
7 prompt "Binary format:"
12 depends on ARCH_USE_MMU || BARE_METAL
14 This will make your system build ELF executables,
15 suitable for architectures with an MMU.
17 config ARCH_BINFMT_FLAT
20 depends on ! ARCH_USE_MMU
22 This will build flat binaries, suitable for
23 MMU-less architectures.
25 config ARCH_BINFMT_FDPIC
28 depends on ! ARCH_USE_MMU
30 This will build FD_PIC ELF binaries, suitable for
31 MMU-less architectures that still require to use
32 shared libraries (FIXME).
39 source "config.gen/binutils.in"
40 source "config.gen/binutils.in.2"