[pywin32-bugs] [ pywin32-Bugs-2907614 ] PYWIN32 not identifying current WINVER correctly (v214)

[SourceForge.net <no...@so...>]

Bugs item #2907614, was opened at 2009-12-02 09:27
Message generated for change (Comment added) made by urban_dk
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2907614&group_id=78018

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: pythonwin
Group: None
Status: Closed
Resolution: None
Priority: 5
Private: No
Submitted By: marvin greenberg (marvingreenberg)
Assigned to: Nobody/Anonymous (nobody)
Summary: PYWIN32 not identifying current WINVER correctly (v214)

Initial Comment:
I'm building python from source, then using that build to build pywin32 from source (to satisfy some requirements of our build environment).  This succeeds fine when the build machine is XP SP2 with VIsualStudio VC90, but when the installed dev env is VC80 it fails.

Python builds and installs fine.  PYWIN32 builds, but as it builds there are a variety of messages "Unable to import verstamp, no version info will be added"  Googling seems to indicate this issue has been resolved, and there is not any error copying, e.g. pywintypes, like

"copying build\temp.win32-2.6\Release\win32\src\pywintypes26.lib -> build\temp.win32-2.6\Release\pywintypes.lib"

When PYWIN32 gets to trying to build win32process extensions, I get 

win32/src/win32process_py2_swig.cpp(2635) : error C2065: 'THREAD_MODE_BACKGROUND_BEGIN' : undeclared identifier
win32/src/win32process_py2_swig.cpp(2637) : error C2065: 'THREAD_MODE_BACKGROUND_END' : undeclared identifier

I also get warnings like:
"cl : Command line warning D9002 : ignoring unknown option '/YXPyWinTypes.h' PyACL.cpp"

Which all seems to imply WINVER is being set to the wrong value.  And indeed early in the build process, I see

"Found version 0x500 in C:\Program Files\Microsoft Visual Studio 8\VC\PlatformSDK\include\WinResrc.h"

Now my VIsual Studio IDE is up to date, and XP SP2 should be 0x500.

Is this some problem with how I'm building PYWIN32 preventing some internal logic from correctly identifying the build platform?
Is there some way to force PYWIN32 to target a specific windows platform?  (I've tried setting CL to /DWINVER=0x502 to no avail)

My actual command line, run under cygwin (yes...) is:

export PATH='/cygdrive/c/Program Files/Microsoft Visual Studio 8/Common7/IDE:/cygdrive/c/Program Files/Microsoft Visual Studio 8/vc/bin:/cygdrive/c/Program Files/Microsoft Visual Studio 8/vc/vcpackages:/cygdrive/c/Program Files/Microsoft Visual Studio 8/Common7/Tools:/cygdrive/c/Program Files/Microsoft Visual Studio 8/Common7/Tools/bin/prerelease:/cygdrive/c/Program Files/Microsoft Visual Studio 8/Common7/Tools/bin:/cygdrive/c/Program Files/Microsoft Visual Studio 8/SDK/v2.0/bin:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS:/cygdrive/c/WINDOWS/System32/Wbem:/usr/bin';  

/cygdrive/c/buildhome/all/xp-vc80/python-vtrunk-2.6.4/build/python setup.py install

using the local built and installed python.

----------------------------------------------------------------------

Comment By: Brad Johnson (urban_dk)
Date: 2010-07-20 14:43

Message:
I get the "undeclared identifier" errors as well, turns out it is because
the Platform SDK provided with VS2003 does not include those #defines. I
think the earliest Platform SDK that defines them is the Vista SDK, which
is "not recommended" for use with VS2003.

It is my understanding that VS2003 is required for building the extension
for Python 2.5 and earlier.

----------------------------------------------------------------------

Comment By: marvin greenberg (marvingreenberg)
Date: 2009-12-03 06:07

Message:
Unsupported configuration.

----------------------------------------------------------------------

Comment By: marvin greenberg (marvingreenberg)
Date: 2009-12-03 06:06

Message:
I sort of suspected that would be the response, but completely understand. 
I was hoping this might have been some simple oversight (which hope had
been essentially extinguished after looking at the complexity of setup.py).
 Thanks.

----------------------------------------------------------------------

Comment By: Mark Hammond (mhammond)
Date: 2009-12-02 13:43

Message:
Note that Python 2.,6 is officially built using VS2008.  Re not finding the
SDK, you may need to set the MSSDK environment variable to point at your
SDK.

----------------------------------------------------------------------

Comment By: marvin greenberg (marvingreenberg)
Date: 2009-12-02 13:16

Message:
There is a typo above -- the expected winver for XP SP2 is 0x502.  

----------------------------------------------------------------------

Comment By: marvin greenberg (marvingreenberg)
Date: 2009-12-02 10:25

Message:
Debugging setup.py a bit, find_platform_sdk_dir() is returning None.  None
of the registry keys or paths exists.  Windows.h is only found under the
Microsoft Visual Studio 8/VC/PlatformSDK/Include

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2907614&group_id=78018