Mercurialcrosstool-ng / file revision
summary | shortlog | changelog | graph | tags | branches | files | changeset | file | latest | revisions | annotate | diff | raw | help
config/libc/mingw.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 3112 6cb56b3f2d34
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 # mingw options

     2 

     3 ## depends on WINDOWS

     4 ##

     5 ## select LIBC_SUPPORT_WIN32THREADS

     6 ## select CC_CORE_PASSES_NEEDED

     7 ##

     8 ## help The de-facto standard for Mingw distributions.

     9 

    10 choice

    11     bool

    12     prompt "Windows API version"

    13 

    14 # Don't remove next line

    15 # CT_INSERT_VERSION_BELOW

    16 config WINAPI_V_2_0_7

    17     bool

    18     prompt "2.0.7"

    19 

    20 config WINAPI_V_select

    21     bool

    22     prompt "Other version"

    23 

    24 endchoice

    25 

    26 config WINAPI_VERSION

    27     string

    28     prompt "Windows API version" if WINAPI_V_select

    29 # Don't remove next line

    30 # CT_INSERT_VERSION_STRING_BELOW

    31     default "2.0.7" if WINAPI_V_2_0_7

    32     help

    33       Enter the version number of the Windows API files to use

    34 

    35 config MINGW_DIRECTX

    36     bool

    37     prompt "Include DirectX development files"

    38 

    39 config MINGW_DDK

    40     bool

    41     prompt "Include DDK development files"
crosstool-ng