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

[Raymond Stewart]

Yes, that's it. I was not actually typing "python" before setup.py.... As a result, instead of resolving to python 2.6 though the PATH assignment, it was resolved with through the windows file association.

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.

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?

Raymond

--- 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-win32/attachments/20090106/1ebf971c/attachment-0001.htm>