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>
3 menu "Operating System"
5 # Config option used throughout the config and code to determine wether
6 # we have a kernel or not (there might be different bare metal stuff)...
13 # Each target OS (aka kernel) that support shared libraries can select
14 # this, so the user can decide whether or not to build a shared library
16 config KERNEL_SUPPORTS_SHARED_LIBS
25 source "config.gen/kernel.in"
27 comment "Common kernel options"
31 prompt "Build shared libraries"
32 depends on KERNEL_SUPPORTS_SHARED_LIBS
35 Say 'y' here, unless you don't want shared libraries.
37 You might not want shared libraries if you're building for a target that
38 don't support it (maybe some nommu targets, for example, or bare metal).
40 source "config.gen/kernel.in.2"