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 # Test suite config options
12 prompt "GCC test suite"
15 Select this option to install the GCC test suite in $CT_PREFIX_DIR/test_suite.
17 The GCC test suite includes a collection of various toolchain tests for GCC -
18 it utilizes the DejaGnu test framework.
20 For some tests a network enabled target with ssh server is required.
22 A helper Makefile is provided for running the tests - please see the included
23 README for information on how to run the test suite.