Mercurialcrosstool-ng / file revision
summary | shortlog | changelog | graph | tags | branches | files | changeset | file | latest | revisions | annotate | diff | raw | help
config/kernel/mingw32.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Sun Mar 20 00:02:21 2011 +0100 (2011-03-20)
changeset 2339 730e2d63296b
parent 2027 38cc05a621f0
child 2444 896cb0d36c1a
permissions -rw-r--r--
scripts: leave changelog in build dir, copy to install dir

Users tend to look for the build log in the current working directory,
rather than in the toolchain's installation dir. While bundling the build
log in the toolchain installation dir is nice for distribution and review,
it can be easier to have the build log readily available in the working
directory, as it is quicker to get to it.

So, the build log stays in the working directory until the toolchain is
completely and successfully built, and then a (compressed) copy is made.

Reported-by: Trevor Woerner <twoerner@gmail.com>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr> 
     1 # mingw32 config options

     2 # depends on EXPERIMENTAL && ( ARCH_x86 && ARCH_32 )

     3 

     4 config KERNEL_mingw32

     5     select MINGW32

     6     help

     7       Build a toolchain targeting systems running Windows as host

     8 

     9 choice

    10     bool

    11     prompt "Windows api version"

    12 

    13 # Don't remove next line

    14 # CT_INSERT_VERSION_BELOW

    15 config W32API_V_3_14

    16     bool

    17     prompt "3.14"

    18 

    19 config W32API_V_select

    20     bool

    21     prompt "Other version"

    22 

    23 endchoice

    24 

    25 config W32API_VERSION

    26     string

    27     prompt "W32 api version" if W32API_V_select

    28 # Don't remove next line

    29 # CT_INSERT_VERSION_STRING_BELOW

    30     default "3.14" if W32API_V_3_14

    31     help

    32       Enter the version number of the windows api files to use

    33
crosstool-ng