We should note that even though we can build cleanly with GTK_DISABLE_DEPRECATED, there are still a lot of deprecated symbols in use. The reason for this is that a lot of Gtkmm headers disable the deprecation flag, so that Gtkmm can continue to use deprecated stuff... so any of our source files that include a gtkmm header before <gtk/gtk.h> can still contain deprecated GTK+ symbols.
The only "true" check is to compile against GTK+3 in which the deprecated symbols have been completely removed. Over to bug #972797 for the real fun!
@John... Thanks very much!
We should note that even though we can build cleanly with GTK_DISABLE_ DEPRECATED, there are still a lot of deprecated symbols in use. The reason for this is that a lot of Gtkmm headers disable the deprecation flag, so that Gtkmm can continue to use deprecated stuff... so any of our source files that include a gtkmm header before <gtk/gtk.h> can still contain deprecated GTK+ symbols.
The only "true" check is to compile against GTK+3 in which the deprecated symbols have been completely removed. Over to bug #972797 for the real fun!