config/companion_libs/mpc.in
author "Yann E. MORIN" <yann.morin.1998@free.fr>
Thu Dec 27 12:45:22 2012 +0100 (2012-12-27)
changeset 3152 b286c7993be5
parent 2957 3e2f2100a76d
child 3220 2685dfa9de14
permissions -rw-r--r--
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 # MPC options
     2 
     3 choice
     4     bool
     5     prompt "MPC version"
     6 # Don't remove next line
     7 # CT_INSERT_VERSION_BELOW
     8 
     9 config MPC_V_0_9
    10     bool
    11     prompt "0.9"
    12 
    13 config MPC_V_0_8_2
    14     bool
    15     prompt "0.8.2"
    16 
    17 
    18 config MPC_V_0_8_1
    19     bool
    20     prompt "0.8.1"
    21 
    22 config MPC_V_0_7
    23     bool
    24     prompt "0.7"
    25 
    26 endchoice
    27 
    28 config MPC_VERSION
    29     string
    30 # Don't remove next line
    31 # CT_INSERT_VERSION_STRING_BELOW
    32     default "0.9" if MPC_V_0_9
    33     default "0.8.2" if MPC_V_0_8_2
    34     default "0.8.1" if MPC_V_0_8_1
    35     default "0.7" if MPC_V_0_7