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 This is a somewhat ordered TODO list:
5 - update versions for every tools...
7 - update and/or upgrade all samples
12 - update newlib (for enhanced bare metal)
13 - confirm existing implementation on targets other than AVR32
14 - try to make it generic, will help for uClibc++
18 - Cygwin target (needs newlib)
19 - so we can build toolchains that generate code for Windows/Cygwin
22 - so we can build toolchains that run natively under Windows/Cygwin
25 - so we can build toolchains that generate code for Windows/Win32
28 - so we can build toolchains that run natively under Windows/Win32
29 (without requiring Cygwin)
35 - check whether we can use newlib under uClinux (?)