Re: Problem

I think you are maybe not using a new-enough version of
glibmm, though
jhbuild should have taken care of that. I have added a check
in
configure.in to make sure of it.


We need this new feature in glibmm:

2007-09-25  Murray Cumming  <murraycmurrayc.com>

	* glib/glibmm/wrap.cc:
	* glib/glibmm/wrap.h: Added wrap_auto_interface<>(),
which should 
	be used by wrap() specializations for interfaces, so we
create 
	instances of the interface even if the derived C type is
unknown to 
	us.
	* glib/glibmm/signalproxy_connectionnode.h: Do not wrap.h
from here 
	unnecessarily, to allow us to include objectbase.h in
wrap.h, 
	needed by the new templated method.
	* tools/m4/class_interface.m4: Use
wrap_auto_interface<>() 
	instead of wrap_auto() for interfaces.


-- 
murraycmurrayc.com
www.murrayc.com
www.openismus.com

_______________________________________________
glom-devel-list mailing list
glom-devel-listgnome.org
http://mail.gnome.org/mailman/listinfo/glom-devel-list

On Sat, 2007-12-01 at 16:10 +0100, Murray Cumming wrote:
> I think you are maybe not using a new-enough version of
glibmm, though
> jhbuild should have taken care of that. I have added a
check in
> configure.in to make sure of it.

Note also that the subsequent libraries (particularly
libgdamm) would
have to be rebuilt after "touch"ing all their .hg
files. The easiest way
would be to just remove them and let jhbuild check them out
again.

But I still wonder how you could have an old glibmm inside
jhbuild.

-- 
murraycmurrayc.com
www.murrayc.com
www.openismus.com

_______________________________________________
glom-devel-list mailing list
glom-devel-listgnome.org
http://mail.gnome.org/mailman/listinfo/glom-devel-list