[issue1706] Force WINVER 0x0500 (Windows 2000)
Nick Coghlan
report at bugs.python.org
Sat Feb 9 16:51:49 CET 2008
Nick Coghlan added the comment:
I thought WINVER defaulted to something like 0x0400 (i.e. you can't use
things specifically defined for even Win2k without setting it, let alone
things first defined for XP).
I know I had to force it to 0x0500 recently for a non-Python project to
get access to the function that permits a non-blocking attempt to
acquire a critical section. That project is stuck using VC6 though -
current MS compilers may default it to something more recent.
----------
nosy: +ncoghlan
__________________________________
Tracker <report at bugs.python.org>
<http://bugs.python.org/issue1706>
__________________________________
More information about the Python-bugs-list
mailing list