> > If you know what you are doing, you can override the logic of distutils.
> > Set up an SDK environment (with LIBRARY, INCLUDE and everything), then
> > also set the MSSdk environment variable (which should get set if you
> > use the standard environment batch file from the SDK), and then also
>
> Either I misunderstand, or you do. If it wasn't clear, I have already
> rebuilt Python using Visual Studio 2005.
I see. I must have misunderstood then - if you already rebuilt Python
itself, all is fine.
Regards,
Martin
--
http://mail.python.org/mailman/listinfo/python-list
> > In order to test this theory (and potentially fix it), I want to re-
> > build the pywin32 stuff using Visual Studio 2005.
>
> That might not be sufficient. You have to rebuild Python itself as well.
Either I misunderstand, or you do. If it wasn't clear, I have already
rebuilt Python using Vis
> Now, my theory on this issue is that DLLs like win32api.pyd, which I
> acquired pre-built, were built with Visual Studio 2003, and they
> depend on msvcr71.dll. My Python/MFC application, on the other hand,
> was built with Visual Studio 2005, and is linking with msvcr80.dll. If
> memory gets all
On Nov 14, 12:41 pm, [EMAIL PROTECTED] wrote:
> Hi everybody...
>
> I'm hoping one of you reading this can help me out here. I'm having
> trouble getting pywin32 to build with Visual Studio 2005. But first,
> some background.
>
> I'm embedding Python in an MFC application. I've manually built
> Pyt
