Build extensions for windows python 2.4 what are the compiler rules?
I see that, as expected, windows python 2.4 was built with MSVC 7.1 rather then msvc 6.0. It seems that I can build extensions with msvc 6.0 that work with the python 2.4 windows binary kit. Is this safe? I recall warning a while ago about mixing msvc 6.0 and msvc 7.1 runtime DLL's. Is this an issue with python 2.4? I'm also surprised that the python 2.4 source kit only mentions MSVC 6.0 and not the compiler that you actually built python 2.4 with. Barry
Barry Scott wrote:
It seems that I can build extensions with msvc 6.0 that work with the python 2.4 windows binary kit.
Is this safe?
No, it isn't. This emerges as a Python 2.4 FAQ.
I recall warning a while ago about mixing msvc 6.0 and msvc 7.1 runtime DLL's. Is this an issue with python 2.4?
Yes, it is.
I'm also surprised that the python 2.4 source kit only mentions MSVC 6.0 and not the compiler that you actually built python 2.4 with.
Why do you say that? PCbuild/readme.txt starts with Building Python using VC++ 7.1 ------------------------------------- This directory is used to build Python for Win32 platforms, e.g. Windows 95, 98 and NT. It requires Microsoft Visual C++ 7.1 (a.k.a. Visual Studio .NET 2003). (For other Windows platforms and compilers, see ../PC/readme.txt.) Regards, Martin
On Dec 23, 2004, at 23:12, Martin v. Löwis wrote:
Barry Scott wrote:
It seems that I can build extensions with msvc 6.0 that work with the python 2.4 windows binary kit. Is this safe?
No, it isn't. This emerges as a Python 2.4 FAQ.
I recall warning a while ago about mixing msvc 6.0 and msvc 7.1 runtime DLL's. Is this an issue with python 2.4?
Yes, it is.
I'm also surprised that the python 2.4 source kit only mentions MSVC 6.0 and not the compiler that you actually built python 2.4 with.
Why do you say that? PCbuild/readme.txt starts with
I recursive grep'ed and missed this ref. However I did read this in README.TXT:
Building on non-UNIX systems ----------------------------
For Windows (2000/NT/ME/98/95), assuming you have MS VC++ 6.0, the project files are in PCbuild, the workspace is pcbuild.dsw. See PCbuild\readme.txt for detailed instructions.
Which says that PCbuild/readme.txt is about VC++ 6.0
Building Python using VC++ 7.1 ------------------------------------- This directory is used to build Python for Win32 platforms, e.g. Windows 95, 98 and NT. It requires Microsoft Visual C++ 7.1 (a.k.a. Visual Studio .NET 2003). (For other Windows platforms and compilers, see ../PC/readme.txt.)
Regards, Martin
Barry
Barry Scott wrote:
I recursive grep'ed and missed this ref. However I did read this in README.TXT:
Building on non-UNIX systems ----------------------------
For Windows (2000/NT/ME/98/95), assuming you have MS VC++ 6.0, the project files are in PCbuild, the workspace is pcbuild.dsw. See PCbuild\readme.txt for detailed instructions.
Which says that PCbuild/readme.txt is about VC++ 6.0
I see. This is now corrected in CVS. Regards, Martin
Barry Scott
I recursive grep'ed and missed this ref. However I did read this in README.TXT:
The top-level README file is hilariously out-of-date, in some ways. I meant to do something about this before 2.4 final, but didn't get around to it... Cheers, mwh -- <exarkun> speak of the devil <moshez> exarkun: froor <exarkun> not you -- from Twisted.Quotes
Hi, On Fri, Dec 24, 2004 at 12:17:49AM +0000, Barry Scott wrote:
I recursive grep'ed and missed this ref. However I did read this in README.TXT:
The "extending and embedding" tutorial is similarily out-of-date. Armin
Armin Rigo
Hi,
On Fri, Dec 24, 2004 at 12:17:49AM +0000, Barry Scott wrote:
I recursive grep'ed and missed this ref. However I did read this in README.TXT:
The "extending and embedding" tutorial is similarily out-of-date.
Well, I've half re-written that (the entire thing, see doc-sig passim) but this hasn't attracted a great deal of interest. I've just uploaded my most recent version to: http://starship.python.net/crew/mwh/toext/ I haven't done any substantial work on it in a while, and probably won't have time to do any for some time. It would still be nice to have it ready in the 2.5 timeframe. Cheers, mwh -- A difference which makes no difference is no difference at all. -- William James (I think. Reference anyone?)
Armin Rigo wrote:
The "extending and embedding" tutorial is similarily out-of-date.
This is now fixed in the CVS, both for PC/example_nt, and for Doc/ext/windows.tex. These files still could stand further correction. I forgot to update the output of the examples to 2.4, and the .def file stuff should be removed from the examples, replacing them with the proper macros. Regards, Martin
participants (4)
-
"Martin v. Löwis" -
Armin Rigo -
Barry Scott -
Michael Hudson