On 13/03/13 07:17, Theuns Heydenrych wrote: > Hi, I know this is not a Python mailing list, but i am desperate. > Someone in StackOverflow > I am compiling Sip and PyQt from source using Mingw64 and Python 2.7.3 > 64bit. > Python binaries is installed via downloaded installer, and is build > with MSVC. > I went through the exercise of making a libpython27.a file. > > Sip build successfully and work when used in a python console when > using the following script > >>> from sip import * > > and PyQt build successfully , but fails with a Python stop working > Windows7 dialog , when the following script is used in the python console. > >>> from PyQt4.Qt import * > > How do i debug this? > Is it because Python is build with MSVC? > > Is it ok, to build things like Sip and PyQt with Mingw and gcc and it > link against a MSVC Python27.dll? Hi,
this is a recurrent topic unfortunately. You can built extensions to MSVC-compiled python with mingw, but the problem is the MSVC runtime you link to - msvcrt or msvcr90 etc. See my post http://article.gmane.org/gmane.comp.gnu.mingw.w64.general/6306 (and the rest of that thread) for solution: change the MSVC dll disutils link to. I did build sip and pyqt4 (among others) successfully, it works flawlessly. (Building SIP was tricky with msys shell a bit.) You might want to check http://permalink.gmane.org/gmane.comp.gnu.mingw.w64.general/6511 - there are build scripts and patches in the attachment which I used. http://bugs.python.org/issue16472 is upstream bug for this. HTH, Vaclav ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
