Mercurialcrosstool-ng / file revision
summary | shortlog | changelog | graph | tags | branches | files | changeset | file | latest | revisions | annotate | diff | raw | help
config/companion_libs/mpc.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Mon Mar 28 01:05:18 2011 +0200 (2011-03-28)
changeset 2362 0888065f8c4d
parent 1985 f04a1f18c2bb
child 2957 3e2f2100a76d
permissions -rw-r--r--
cc/gcc: cleanup the _or_later logic

So far, we've had a version always select appropriate _or_later option,
which in turn would select all previous _or_later options.

Because the dependencies on companion libs were cumulative, that was
working OK. But the upcoming 4.6 will no longer depend on libelf, so
we can't keep the cumulative scheme we've been using so far.

Have each release family select the corresponding dependencies, instead
of relying on selecting previous _or_later.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.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 (EXPERIMENTAL)"

    12     depends on EXPERIMENTAL

    13 

    14 config MPC_V_0_8_2

    15     bool

    16     prompt "0.8.2 (EXPERIMENTAL)"

    17     depends on EXPERIMENTAL

    18 

    19 config MPC_V_0_8_1

    20     bool

    21     prompt "0.8.1"

    22 

    23 config MPC_V_0_7

    24     bool

    25     prompt "0.7"

    26 

    27 config MPC_V_0_6

    28     bool

    29     prompt "0.6 (OBSOLETE)"

    30     depends on OBSOLETE

    31 

    32 endchoice

    33 

    34 config MPC_VERSION

    35     string

    36 # Don't remove next line

    37 # CT_INSERT_VERSION_STRING_BELOW

    38     default "0.9" if MPC_V_0_9

    39     default "0.8.2" if MPC_V_0_8_2

    40     default "0.8.1" if MPC_V_0_8_1

    41     default "0.7" if MPC_V_0_7

    42     default "0.6" if MPC_V_0_6
crosstool-ng