Mercurialcrosstool-ng / file revision
summary | shortlog | changelog | graph | tags | branches | files | changeset | file | latest | revisions | annotate | diff | raw | help
config/backend.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 1877 b579a5cb53d1
child 2484 d1a8c2ae7946
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 # Options specific to crosstool-NG acting as a backend

     2 

     3 config IS_A_BACKEND

     4     string

     5     option env="CT_IS_A_BACKEND"

     6 

     7 config BACKEND

     8     bool

     9     default y if IS_A_BACKEND =  "y" || IS_A_BACKEND =  "Y"

    10     default n if IS_A_BACKEND != "y" && IS_A_BACKEND != "Y"

    11 

    12 config BACKEND_ARCH

    13     string

    14     option env="CT_BACKEND_ARCH"

    15 

    16 config BACKEND_KERNEL

    17     string

    18     option env="CT_BACKEND_KERNEL"

    19 

    20 config BACKEND_LIBC

    21     string

    22     option env="CT_BACKEND_LIBC"
crosstool-ng