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>
yann@1384
     1
# MPC options
yann@1384
     2
yann@1384
     3
choice
yann@1384
     4
    bool
yann@1384
     5
    prompt "MPC version"
yann@1535
     6
# Don't remove next line
yann@1535
     7
# CT_INSERT_VERSION_BELOW
yann@1384
     8
yann@2319
     9
config MPC_V_0_9
yann@2319
    10
    bool
yann@2957
    11
    prompt "0.9"
yann@2319
    12
yann@1985
    13
config MPC_V_0_8_2
yann@1985
    14
    bool
yann@2957
    15
    prompt "0.8.2"
yann@2957
    16
yann@1985
    17
yann@1695
    18
config MPC_V_0_8_1
yann@1695
    19
    bool
yann@1783
    20
    prompt "0.8.1"
yann@1695
    21
yann@1534
    22
config MPC_V_0_7
yann@1534
    23
    bool
yann@1534
    24
    prompt "0.7"
yann@1534
    25
yann@1384
    26
endchoice
yann@1384
    27
yann@1384
    28
config MPC_VERSION
yann@1384
    29
    string
yann@1535
    30
# Don't remove next line
yann@1535
    31
# CT_INSERT_VERSION_STRING_BELOW
yann@2319
    32
    default "0.9" if MPC_V_0_9
yann@1985
    33
    default "0.8.2" if MPC_V_0_8_2
yann@1695
    34
    default "0.8.1" if MPC_V_0_8_1
yann@1534
    35
    default "0.7" if MPC_V_0_7