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 # Menu for the native gdbserver
6 depends on ! BARE_METAL
8 Build and install a gdbserver for the target, to run on the target.
12 config GDB_GDBSERVER_HAS_IPA_LIB
14 depends on GDB_7_2_or_later
17 config GDB_GDBSERVER_STATIC
19 prompt "Build a static gdbserver"
22 In case you have trouble with dynamic loading of shared libraries,
23 you will find that a static gdbserver comes in handy.
25 config GDB_GDBSERVER_BUILD_IPA_LIB
27 prompt "Build the IPA library"
28 depends on GDB_GDBSERVER_HAS_IPA_LIB && !GDB_GDBSERVER_STATIC
30 gdbserver >= 7.2 comes with an optional library to use tracepoints,
31 the In Process Agent (IPA) library, libinproctrace.so.
33 Say 'y' if you indend to use tracepoints when debugging your
34 programs with gdbserver.
36 Note: Currently, building this library is not possible when the
37 gdbserver is built statically. This is a limitation in
38 crosstool-NG, so do not bug upstream about it...
43 comment "In bare-metal, you'll need to "
44 comment "provide your own gdbserver stub."