From: Steve K. <st...@st...> - 2004-12-03 00:01:33
|
Mikhail Ramendik wrote: >>>Unfortunately, I do not know how to cleanly remove wxGTK 2.5CVS ; make >>>uninstall does nothing. >>> >>> >>For a start, try this: >> >> > >Nothing worked! I am now sure that I am using both wxGTK and gtk+ from RPM. > >I used #ifdef/#warning to understand at which point __WXGTK20__ gets defined >in the main.cc file. And it's this line: > >#include "wx/wxprec.h" > >For reference, the parameters used for cflags: > >$ wx-config --cflags >-I/usr/lib/wx/include/gtk2-2.4 -DGTK_NO_CHECK_CASTS -D__WXGTK__ >-D_FILE_OFFSET_BITS=64 -D_LARGE_FILES > >$ gtk-config --cflags >-I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include >-I/usr/X11R6/include > >Apparently the variable is defined because, indeed, this version of wxWindows >is for gtk2. Now, iaxcomm also links against gtk+ (not gtk2) directly, and >this causes a collision. > >Of course I can use #undef to hack around this. But it's a very dirty >solution, with unpredictable results. Is there a better way? And, perhaps >linking against gtk+ directly is Just Not Right? > > Yes, the problem does look like your wxWindows is built with GTK2 stuff -- I've never tested this before, because it seemed experimental at the time.. so, I don't have this problem, but here are some solutions: 1) try taking out the gtk-config things altogether; I'm not sure if they're necessary.. 2) try replacing the gtk-config stuff with "pkg-config gtk+-2.0 --cflags" etc. (i.e. replace "gtk-config" with "pkg-config gtk+-2.0". -SteveK |