[wx-dev] wxPython built on windows with GCC (cygwin/mingw)

[Robin Dunn]

Edouard TISSERANT wrote:
> Hello.
> 
> I'm Edouard TISSERANT, from the wxSVG (www.wxsvg.org) project (svg
> renderer for wx with python bindings).
> It works smoothly on Linux, and I've tried to port python wrappers to
> windows.
> 
> It is not possible to link C++ libraries from both VC++ and GCC. In
> other words to build C++ extensions for wxPython on windows require
> wxPython to be compiled with GCC, not visual studio.
> 
> This is the reason why I ported wxPython to mingw32 (using cygwin as a
> posix shell).
> 
> It is almost working but an important bug remain, and I can't solve it :
> It only works in python interactive mode ( python.exe -i ), typing code
> line one after the other...
> 
> I've written a wiki page for the whole procedure here :
> http://www.mingw.org/cms/node/17

Well after waiting forever for the compiles to finish (now I appreciate 
the speed of MSVC *much* more than before!) I'm not able to duplicate 
the crash you are seeing.  Does it also crash if you do "python 
sample.py" instead of using the execfile() from within the interactive 
interpreter?  I'm able to run everything in the demo that I tried, 
(except for the things that were automatically excluded by configure or 
build options of course.)

My build is not an exact duplicate of yours.  I used the current 2.8 
branch from the subversion repository, and I also changed some of your 
instructions/patches along the way as I integrated them into my sources 
to be more consistent and easier to coexist with the MSVC build code. 
But I don't think I changed anything that would have changed a crashing 
situation into a non-crashing one.

Anyway, I should have all this available in the 2.8.6.1 release in a few 
days, along with an updated BUILD.txt file.  Thanks a lot for your work 
on this, I was a bit surprised that it required as few changes to 
config.py as it does, and I was pleased to see that Python 2.5 already 
includes the libpython25.a file now instead of requiring us to generate 
it as in earlier versions.  Now if it just didn't take 6 times as long 
(that's not an exaggeration, it's a very conservative guess) to compile 
wx and wxPython as MSVC does it might actually be worth using it.  ;-)

-- 
Robin Dunn
Software Craftsman
http://wxPython.org  Java give you jitters?  Relax with wxPython!