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>
2 %define hash-function-name kconf_id_hash
3 %define lookup-function-name kconf_id_lookup
4 %define string-pool-name kconf_id_strings
12 static struct kconf_id *kconf_id_lookup(register const char *str, register unsigned int len);
15 mainmenu, T_MAINMENU, TF_COMMAND
16 menu, T_MENU, TF_COMMAND
17 endmenu, T_ENDMENU, TF_COMMAND
18 source, T_SOURCE, TF_COMMAND
19 choice, T_CHOICE, TF_COMMAND
20 endchoice, T_ENDCHOICE, TF_COMMAND
21 comment, T_COMMENT, TF_COMMAND
22 config, T_CONFIG, TF_COMMAND
23 menuconfig, T_MENUCONFIG, TF_COMMAND
24 help, T_HELP, TF_COMMAND
25 if, T_IF, TF_COMMAND|TF_PARAM
26 endif, T_ENDIF, TF_COMMAND
27 depends, T_DEPENDS, TF_COMMAND
28 optional, T_OPTIONAL, TF_COMMAND
29 default, T_DEFAULT, TF_COMMAND, S_UNKNOWN
30 prompt, T_PROMPT, TF_COMMAND
31 tristate, T_TYPE, TF_COMMAND, S_TRISTATE
32 def_tristate, T_DEFAULT, TF_COMMAND, S_TRISTATE
33 bool, T_TYPE, TF_COMMAND, S_BOOLEAN
34 boolean, T_TYPE, TF_COMMAND, S_BOOLEAN
35 def_bool, T_DEFAULT, TF_COMMAND, S_BOOLEAN
36 int, T_TYPE, TF_COMMAND, S_INT
37 hex, T_TYPE, TF_COMMAND, S_HEX
38 string, T_TYPE, TF_COMMAND, S_STRING
39 select, T_SELECT, TF_COMMAND
40 range, T_RANGE, TF_COMMAND
41 visible, T_VISIBLE, TF_COMMAND
42 option, T_OPTION, TF_COMMAND
44 modules, T_OPT_MODULES, TF_OPTION
45 defconfig_list, T_OPT_DEFCONFIG_LIST,TF_OPTION
46 env, T_OPT_ENV, TF_OPTION