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@anciens.enib.fr>
Thu Dec 23 20:43:32 2010 +0100 (2010-12-23)
changeset 2307 2efd46963086
child 2444 896cb0d36c1a
permissions -rw-r--r--
buildtools: move to working directory

There is absolutely *no* reason for the buildtools (wrappers to gcc, g++,
as, ld... for the local machine) to be in the toolchain directory. Moreover,
they are removed after the build completes.

Move them out of the toolchain directory, and into the build directory (but
yet the part specific to the current toolchain). This means we no longer
need to explicitly remove them either, BTW, but we need to save/restore them
for the restart feature.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr> 
     1 # mingw options

     2 # depends on MINGW32

     3 

     4 config LIBC_mingw

     5     bool

     6     select LIBC_SUPPORT_WIN32THREADS

     7     help

     8       The de-facto standard for Mingw distributions.

     9 

    10 choice

    11     bool

    12     prompt "Mingw runtime version"

    13 

    14 # Don't remove next line

    15 # CT_INSERT_VERSION_BELOW

    16 config MINGWRT_V_3_18

    17     bool

    18     prompt "3.18"

    19 

    20 config MINGWRT_V_select

    21     bool

    22     prompt "Other version"

    23 

    24 endchoice

    25 

    26 config MINGWRT_VERSION

    27     string

    28     prompt "Mingw runtime version" if MINGWRT_V_select

    29 # Don't remove next line

    30 # CT_INSERT_VERSION_STRING_BELOW

    31     default "3.18" if MINGWRT_V_3_18

    32     help

    33       Enter the version number of the mingw runtime files to use

    34
crosstool-ng