|
Nicolas Lehuen
nicolas at lehuen.com
Mon Dec 6 03:49:14 EST 2004
> -----Message d'origine----- > De : David Fraser [mailto:davidf at sjsoft.com] > Envoyé : lundi 6 décembre 2004 08:12 [...] > >OK, I've managed to rebuild mod_python.so for Win32 with Python 2.4 > >support, and it seems to work properly. If you want the > binary version, > >write me and I'll send it to you. Note that I've tried it on Apache > >2.0.52 compiled with VC 7.1 too, so your mileage may vary if > you have > >the standard build of Apache. > > > >The problem is that I could not rebuild _psp.pyd, so PSP > pages are not > >working for now. Until now, I only needed to rebuild mod_python.so > >since the patches I wrote were targeting this module, so I've just > >noticed that building _psp.pyd is not as straightforward as building > >mod_python.so, mainly because there are no project file or > setup.py for > >this. It seems that the subversion repository misses > something there. > >Grisha, can you tell us how to rebuild _psp.pyd ? > > > > > Glad someone has done this. Could you include the details of > how you built it? > > You may also want to try the modifications I did to > setup.py.in which enables it to build the extensions > > It's in the mailing list archives but I've attached my latest > version here in case. > > David Well, actually rebuilding mod_python.so using Visual Studio .NET 2003 is quite easy, you just have to open the .vcproj file which is in the subversion repository, convert it to a VC 7.1 project, fiddle with the path setting to point to the Python 2.4 installation and you're done. You get a bunch of warnings (about 50 warning related to "inconsistent DLL reference" or something like that) but the final binary is usable. Well, at least the Python 2.3 version that I've built in the same way is usable since I've been using it in production for a few months now ; I have just made a few tests with the Python 2.4 version and it seems OK. I'll give a try to your setup.py.in modifications since I'd rather find a way to build a win32 version without using the .vcproj file, which requires the full Visual Studio .NET 2003 I think... Being able to use the free Microsoft compiler or MinGW is much more democratic. Regards, Nicolas
|