The GTK folks broke binary compatibility with 1.2.8. You'll either have to
rebuild everything yourself or move back a rev or two of gtk and glib (I use
1.2.6).
> On my Linux box I installed
>
> glib 1.2.8
> gtk 1.2.8
> wxGTK 2.1.16
> wxPython 2.1.16
>
> (in the order listed above, all from source).
^^^^^^^^^^^^^^^^
I didn't see that comment before. In this case I'm not sure. I read on
wx-devel that it had been fixed, maybe there is a newer version of the wxGTK
sources that has the fix. Try getting ftp://wesley.informatik.uni-freiburg.de/pub/linux/wxxt/source/wxGTK-2.1.16.t
gz and rebuilding it. If that doesn't help then try asking on
wx-devel@wxwindows.org.
The GTK folks broke binary compatibility with 1.2.8. You'll either have to
rebuild everything yourself or move back a rev or two of gtk and glib (I use
1.2.6).
Thanks. I will try that.
This answer made me think a little. After previous "trouble" with GTK
(pure GTK, not related to wxWindows/wxPython) I am wondering: is there a
wxPython binding to wxMotif? So far I found only the one to wxGTK.
If this is not done (yet), how hard would it be to tweak the SWIG files?
I am wondering: is there a
wxPython binding to wxMotif? So far I found only the one to wxGTK.
If this is not done (yet), how hard would it be to tweak the SWIG files?
wxMotif is not as complete as wxGTK, so there will be a fair amount of
methods and things that need to get ifdef'ed out. Also there are some
tweaks that need to get done to the wxMotif initialization code so wxPython
can call the right bits when the module is loaded.