On 2012-10-04 10:26, Michael Petch wrote: > I seem to recall that GNUBG may have been using > functionality only supplied in GTK2.10+ and higher. I'm not 100% sure of > this, but I do remember an aha moment that suggested we may not be > compatible with GTK2.6
I have confirmed that GNUBG does require GTK+2.10 or higher . The configure.in file of course says we require 2.6 . It is wrong. The code that requires us to use GLIB2.10 or greater is in gtkgamelist.c g_object_ref_sink only exists in 2.10+ . This is in fact easy to fix with a rather trivial ifdef to make it work with 2.6 There is a function that is only available in GTK+2.8 and higher and that is in gtkprefs.c. The function in question is gtk_tree_view_get_visible_range . Given where we use this function, I can think of a less efficient way of doing it (that would be easy to implement) that would likely suffice for retaining backwards compatibility with 2.6. We could use the less efficient method with with versions vuilt with GTK+ < 2.8 . I have successfully built GNUBG on a Fedora Core system running GTK+2.6 (correcting these 2 issues) With these two mods we could allow GNUBG to be compiled with GTK+2.6 . The problem then becomes one of building it on Win32. GTK+2.6 libraries and headers were built for Win2 platform so it is conceivable with some effort one could create a build environment that would work. Not sure how long it would take (never know what SNAFUs one may encounter). Even if I did get it to build I'd likely consider releasing a separate 2.6 build that would specifically target older OSes. As for trying to replace the newer DLL's with older ones probably will fail to function as expected given that we do (at present) use functions only available in GTK+ releases >= 2.10 . -- Michael Petch CApp::Sysware Consulting Ltd. OpenPGP FingerPrint=D81C 6A0D 987E 7DA5 3219 6715 466A 2ACE 5CAE 3304 _______________________________________________ Bug-gnubg mailing list Bug-gnubg@gnu.org https://lists.gnu.org/mailman/listinfo/bug-gnubg
