On Thu, 2013-07-04 at 17:00 +0200, Kjell Ahlstedt wrote: > 2013-07-01 13:26, Murray Cumming skrev: > > On Sun, 2013-06-30 at 10:46 +0200, Kjell Ahlstedt wrote: > >> If you don't build gtkmm from the latest sources in the git repository, > >> you can stop reading here. > >> > >> During the last few days many functions and some whole classes have been > >> deprecated in gtk+, causing gtkmm builds to fail if > >> --enable-warnings=fatal. > >> I'm working on fixing this (by deprecating a lot of stuff in gtkmm), but > >> it will take some time. It feels like I'm shooting at a moving target > >> right now. There are more deprecations in gtk+ almost each day. The > >> deprecations are not yet consistent. There are still several > >> non-deprecated gtk+ functions that take a parameter of a deprecated class. > > There's a good chance that the GTK+ developers don't know that, so do > > file GTK+ bugs, please. > I have filed gtk+ bug https://bugzilla.gnome.org/show_bug.cgi?id=703616.
Wow. I just looked at the gtkmm changes in git. There really are a lot of new deprecations in GTK+. Many thanks for dealing with it. However, I just tried to do a release and got: enums.cc: In static member function 'static bool Gtk::IconSize::lookup(Gtk::IconSize, int&, int&, const Glib::RefPtr<Gtk::Settings>&)': enums.cc:53:65: error: no matching function for call to 'unwrap(const Glib::RefPtr<Gtk::Settings>&)' -- Murray Cumming [email protected] www.murrayc.com www.openismus.com _______________________________________________ gtkmm-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/gtkmm-list
