It's the mingw-w64-i686-headers-git package where it's defined. Generally
partial upgrades of MSYS2 are not supported but if you to be on your own
keep in mind crt, headers or winpthreads always have to be in the same
version.
MSYS2 had to bump WINNT because some package require Windows 7 features and
older Windows versions are EOL.

czw., 10 sty 2019 o 13:33 Tempelaar E. (Erik) <erik.tempel...@vanoord.com>
napisał(a):

> I recently reconfigured a build environment for a mingw-built application
> but I ran into issues
> on Windows 10 caused by a #define _WIN32_WINNT in
> C:\msys64\mingw32\i686-w64-mingw32\include\_mingw.h
>
> In my installation it targets WINNT 0x0601
>
> #ifndef _WIN32_WINNT
> #define _WIN32_WINNT 0x601
> #endif
>
> My colleague's setup targets 0x0502.
>
> In my understanding 0x0502 is still the default:
> https://mingw-w64.org/doku.php/configure
>
> https://github.com/mirror/mingw-w64/blob/d72c4fe62568a216d52dca47ca8bace4e220d84f/mingw-w64-headers/configure.ac#L156
>
> I installed msys2-x86_64-20161025.exe and updated via pacman and installed
> i.e. base-devel and pacman -S mingw-w64-i686-gcc.
>
> How could I have ended up with 0x0601?
>
> What's the recommended way to control this and prevent issues like this?
>   Store an archive of msys2/mingw32 somewhere?
>   Add -D_WIN32_WINNT=0x0502 to our makefile?
>
> Here's a (subset) of possible updates for my colleague's setup, my guess
> is that the change is in one of these:
>
> mingw-w64-i686-ca-certificates 20170211-2 -> 20180409-1
> mingw-w64-i686-crt-git 6.0.0.5176.1fd1a585-1 -> 7.0.0.5285.7b2baaf8-1
> mingw-w64-i686-expat 2.2.5-1 -> 2.2.6-1
> mingw-w64-i686-gcc 7.3.0-2 -> 7.4.0-1
> mingw-w64-i686-gcc-libs 7.3.0-2 -> 7.4.0-1
> mingw-w64-i686-gdb 8.1-3 -> 8.2.1-1
> mingw-w64-i686-gettext 0.19.8.1-4 -> 0.19.8.1-7
> mingw-w64-i686-headers-git 6.0.0.5176.1fd1a585-1 -> 7.0.0.5285.7b2baaf8-1
> mingw-w64-i686-libwinpthread-git 6.0.0.5174.9726fb77-1 ->
> 7.0.0.5273.3e5acf5d-1
> mingw-w64-i686-ncurses 6.1.20180526-1 -> 6.1.20180908-1
> mingw-w64-i686-openssl 1.0.2.o-1 -> 1.1.1.a-1
> mingw-w64-i686-p11-kit 0.23.12-1 -> 0.23.14-1
> mingw-w64-i686-python3 3.7.0-10 -> 3.7.2-1
> mingw-w64-i686-sqlite3 3.24.0-1 -> 3.26.0-1
> mingw-w64-i686-tcl 8.6.8-1 -> 8.6.9-2
> mingw-w64-i686-tk 8.6.8-1 -> 8.6.9.1-1
> mingw-w64-i686-winpthreads-git 6.0.0.5174.9726fb77-1 ->
> 7.0.0.5273.3e5acf5d-1
> mingw-w64-i686-zlib 1.2.11-3 -> 1.2.11-5
>
> Please advise, I would like to know how this is supposed to work for
> msys2/mingw32
>
> Kind regards
>
>
>
>
>
> Disclaimer: This mail transmission and any attached files are confidential
> and are intended for the addressee only. If you are not the person or
> organization to whom it is addressed, you must not copy, disclose,
> distribute or take any action in reliance upon it. If you have received
> this message in error, please contact the sender by email and delete all
> copies of this message and all copies of any attached files.
>
> _______________________________________________
> Mingw-w64-public mailing list
> Mingw-w64-public@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>

_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Reply via email to