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 if ! KERNEL_LINUX_USE_CUSTOM_HEADERS
7 prompt "Kernel verbosity:"
8 default KERNEL_LINUX_VERBOSITY_0
10 config KERNEL_LINUX_VERBOSITY_0
14 Print simplified command lines.
16 config KERNEL_LINUX_VERBOSITY_1
18 prompt "Full commands"
20 Print full command lines.
22 config KERNEL_LINUX_VERBOSITY_2
26 Print the reasons why a make target is rebuild.
30 config KERNEL_LINUX_VERBOSE_LEVEL
32 default 0 if KERNEL_LINUX_VERBOSITY_0
33 default 1 if KERNEL_LINUX_VERBOSITY_1
34 default 2 if KERNEL_LINUX_VERBOSITY_2
36 config KERNEL_LINUX_INSTALL_CHECK
38 prompt "Check installed headers"
41 If you are in doubt that installed headers are buggy, say 'Y'
42 here to have an extra check passed onto the headers.
44 endif # ! KERNEL_LINUX_USE_CUSTOM_HEADERS