You're right, the latest version of glibmm (gmmproc) generates erroneous
code. I thought it was an old version that did that. This is something I
should look into, I think.
Anyway, you will have other problems if you let a new version of gmmproc
generate code for gtkmm 2.24.4. That's what bug 697835 is all about.
Gtkmm 2.24.4 (and probably all versions of gtkmm-2) must have its code
generated by an old version of gmmproc that adds
#include <glibmm.h>
to all generated .h files. New versions of gmmproc, from 2.31.0.1
(2011-10-26), adds
#include <glibmm/ustring.h>
#include <sigc++/sigc++.h>
That change was done to speed up compilation, but #include directives
had to be added in many .hg files in gtkmm and other modules.
Kjell
2013-08-12 20:04, John Emmas skrev:
On 12/08/2013 18:25, Kjell Ahlstedt wrote:
It depends on which version of glibmm (and thus gmmproc) you use. The
same bug is mentioned in
https://bugzilla.gnome.org/show_bug.cgi?id=697835#c16 (glibmm version
unknown).
https://bugzilla.gnome.org/show_bug.cgi?id=697835#c21 shows a
different result with glibmm 2.32.0.
The gtkmm 2.24.4 tarball shows a third result (glibmm version
unknown). All of https://bugzilla.gnome.org/show_bug.cgi?id=697835
discusses problems with gtkmm 2.24.3. Version 2.24.4 was released as
a result of those problems. It rurned out that it's important to use
the correct version of glibmm (gmmproc). Unfortunately I can't find
it mentioned in the bug what version of glibmm is the correct one to
use. Does anyone know?
Thanks for the quick response Kjell. It's getting a bit late in my
part of the world (and I've had a long day!) but I'll be sure to
follow up those leads tomorrow. FWIW my copy of gmmproc is only about
2 weeks old (dated 27 Jul 2013) and comes from glibmm version 2.37.4
Can't you use the tarball? Nothing has been added to git branch
gtkmm-2-24 since tarball gtkmm 2.24.4 was released.
Yes, I can definitely use the tarball if all else fails but it'd be
nice to see a fix so that the "hg" file can get built correctly. BTW
'widget.cc' also seems to suffer from a similar problem when
auto-generated :-(
John
_______________________________________________
_______________________________________________
gtkmm-list mailing list
gtkmm-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtkmm-list
