[python-win32] building pywin32 for python 2.6...

Mark Hammond mhammond at skippinet.com.au
Tue Jan 6 23:52:48 CET 2009


> Does the setup file automatically choose the compiler based on the 
> version of python? It seems so as now the compile is running through 
> VS2008 Express.

Yes - you don't need to set a compiler environment - it should "just work".

> Next question. The build fails trying to include afxres.h. This is a MFC
head. 
> Neither VS2008 or the Windows Platform SDK include MFC library files any
more. 
> Is this a deal killer? Do I now need the Full VS2008 Package? Or is
something 
> else wrong?

It means that pythonwin will not be able to be built, but that's not really
a deal-killer - although it might be for the build process!  It will
probably be necessary to comment that project out from setup.py to allow the
rest of the projects to build.  MFC and ATL only come with the full version
IIUC.

Mark


--- On Tue, 1/6/09, Mark Hammond <skippy.hammond at gmail.com> wrote:
From: Mark Hammond <skippy.hammond at gmail.com>
Subject: Re: [python-win32] building pywin32 for python 2.6...
To: apocalypse2012 at yahoo.com
Cc: python-win32 at python.org
Date: Tuesday, January 6, 2009, 3:59 PM
On 6/01/2009 8:04 AM, Raymond Stewart wrote:
> C:\Users\raymond.stewart\Desktop\pywin32-212>setup.py
-q build

Try explicitly putting the full path to the python 2.6 python.exe on the
command-line - I'm guessing '.py' is associated with Python 2.5 (and
on Python 2.5 and earlier, you will need to manually install the most recent
"Platform SDK"; the ones with the older compilers are too old)

Mark




More information about the python-win32 mailing list