config/backend.in
author "Yann E. MORIN" <yann.morin.1998@free.fr>
Thu Jan 24 22:21:19 2013 +0100 (2013-01-24)
changeset 3174 239ea86a47f6
parent 1878 2c577664a23d
permissions -rw-r--r--
cc/gcc: remove 'sub-level' version form symbols

Now we use defconfig files to store the samples, we have to be a bit more
conservatives in the symbols names, so as to avoid gigantic version bumps
when updating sub-level versions from a package.

For example (using fictitious versions):
- in crosstool-NG 1.17.0, we choose:
- latest gcc is gcc-linaro-4.7-2012.10, which is the default for the
choice in the menuconfig
- gcc-linaro-4.6-2012.10 is selected
- so, sample has an explicit symbol for the selected gcc version, as it
is not the default
- we update to crosstool-NG 1.18.0:
- latest gcc version is gcc-linaro-4.7-2013.01
- gcc-linaro-46 has been updated to gcc-linaro-4.6-2013.01
- as the sample now has no *valid* symbol to set the gcc version, the
default is used, while we would have expected to still use the 4.6
release from linaro, not the 4.7

Get rid of sub-level (ie. the third digit sequence in versions) from the
symbols for linaro versions.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
yann@1869
     1
# Options specific to crosstool-NG acting as a backend
yann@121
     2
yann@1842
     3
config IS_A_BACKEND
yann@1842
     4
    string
yann@1842
     5
    option env="CT_IS_A_BACKEND"
yann@1842
     6
yann@1842
     7
config BACKEND
yann@1842
     8
    bool
benoit@2484
     9
    default y if IS_A_BACKEND = "y" || IS_A_BACKEND = "Y"
yann@1842
    10
yann@1868
    11
config BACKEND_ARCH
yann@1868
    12
    string
yann@1868
    13
    option env="CT_BACKEND_ARCH"
yann@1868
    14
yann@1868
    15
config BACKEND_KERNEL
yann@1868
    16
    string
yann@1868
    17
    option env="CT_BACKEND_KERNEL"
yann@1878
    18
yann@1878
    19
config BACKEND_LIBC
yann@1878
    20
    string
yann@1878
    21
    option env="CT_BACKEND_LIBC"