On Mon, 2011-10-17 at 17:00 +0200, Murray Cumming wrote: > glibmm can build again now that the glib change was reverted, but we > still use several deprecated functions in Glib::Thread. It would be > great if someone investigated how we could do it properly, even if > that > means creating a Glib::Thread2.
I instead created a Glib::Threads namespace and put everything in there, deprecating the old stuff: http://git.gnome.org/browse/glibmm/commit/?id=768123b31049e1164a50eb22af8b4c4b4fd46d72 I have no idea if it works, so I would be glad if people would test it, please. Unfortunately, glibmm now does not build with --enable-warnings=fatal: template <class T> inline Private<T>::Private(typename Private<T>::DestructorFunc destructor_func) { //TODO: This causes this warning: //extended initializer lists only available with -std=c++0x or -std=gnu ++0x //See glib bug: https://bugzilla.gnome.org/show_bug.cgi?id=664618 //We can work around this by building like so: //./configure --prefix=/opt/gnome30 'CXXFLAGS=-std=c++0x' gobject_ = G_PRIVATE_INIT(destructor_func); } And if you use -std=c++0x then you will need to remove && !defined(__STRICT_ANSI__) from the GLIBMM_INITIALIZE_STRUCT macro: http://git.gnome.org/browse/glibmm/tree/glib/glibmm/utility.h#n33 -- [email protected] www.murrayc.com www.openismus.com
_______________________________________________ gtkmm-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gtkmm-list
