yes indeed, I'm using MSVC2010. thanks for the warnings, I noticed too late that python itself is compiled with MSVC2008.
I'm going to try to build everything from source, since I want to have full control over the stack, to be able to trace segfaults down. On Fri, 2010-10-01 at 09:00 +0100, Phil Thompson wrote: > On Fri, 01 Oct 2010 09:21:27 +0200, Erik Janssens > <erik.janss...@conceptive.be> wrote: > > I made some changes to sipconfig.py to get it running... > > > > On Thu, 2010-09-30 at 22:26 +0100, Phil Thompson wrote: > >> On Thu, 30 Sep 2010 23:19:24 +0200, Erik Janssens > >> <erik.janss...@conceptive.be> wrote: > >> > Hi, > >> > > >> > I'm trying to build PyQt on Windows, because I want a QT 4.7 build > >> > with OpenSSL included. And I try to build them all with the same > >> > MS compiler, to be able to debug everything afterwards. > >> > > >> > So far OpenSSL, QT and SIP build fine, but when I try to configure > >> > PyQt, it only recognizes the QtCore module. > >> > > >> > It seems as if wrong compiler options are generated, eg there is > >> > a compiler option '-lQtNetwork4' which gets dismissed, and afterwards > >> > symbols in that library are not found. > >> > > >> > Are these options generated by the configure script or by qmake, and > >> > can I change them somewhere ?? > >> > >> That command line is a weird combination of MSVC and MinGW flags. Are > you > >> sure everything has been built with the same compiler? > >> > >> Phil > > So you are using MSVC2010? Note the usual caveats about using Python and > extension modules built with different versions of MSVC. > > Phil _______________________________________________ PyQt mailing list PyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
