[wx-dev] wxGTK flexibility and wxPython

[Robin Dunn]

Gilles Dartiguelongue wrote:
> Le mercredi 05 juillet 2006 à 13:19 +0900, Gilles Dartiguelongue a
> écrit :
>> Le mardi 04 juillet 2006 à 20:07 -0700, Robin Dunn a écrit :
>>> wxPython assumes that it's being built with a fairly full implementation 
>>> of wxWidgets, and so only a few things are conditionalized at 
>>> compile-time.  If you don't mind getting your hands dirty though it's 
>>> not too hard to #ifdef things out that you don't need.  Just edit the .i 
>>> files and then rebuild using the flags that will cause SWIG to be run. 
>>> You'll also need a patched version of SWIG to generate the code 
>>> correctly.  See the wxPython build docs for details.
>>>
>> I'll look into the source code and if I can come up with a patch, I'll
>> post it here.
> 
> After some hours of work, I came up with the attached patch to remove
> TIFF code from the core but then, I have some compile error that
> persists and I can't get rid of them. (see attached file)
> 
> As for swig, I don't know if I need the patches since I'm using 1.3.29.

There were some changes in how the SWIG runtime works in 1.3.29, and 
wxPython 2.6.x isn't updated to be able to work with those changes.  So 
wxPython 2.6.x requires SWIG 1.3.27.  At least the first few errors you 
listed are due to using the newer SWIG.

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