I believe the problem you have there is that you have nested namespaces and there was a discussion sometime ago which said that GIR doesn't support it, although I don't know if specifying the gir namespace should avoid it. At that discussion (it's "Support for custom attribute introspection/reflection?" if you want to search for it) they pointed to this bug https://bugzilla.gnome.org/show_bug.cgi?id=576327
I believe that is your issue, but I'm no expert, I just found your problem familiar. Regards On Mon, Nov 7, 2011 at 23:09, Daniel Espinosa <[email protected]> wrote: > I'm seeing at GXml project (http://git.gnome.org/browse/gxml), and I > found that it uses two Namespaces to define its classes. But GXml > namespace don't have any class defined (yet), I suppose will be used > to define new modules after DOM is finished (may be XSD or others). > But when I try to generate GIR and typelib files, it tries to include > GXml module from outside (and doesn't exists of course) and Dom is > located inside GXml namespace. The next example generate a GIR file > but refuse to create typelib because GXml include fails. > > Is this the expected behavior or what is the better to do on Multiple > and incomplete namespaces? > > > This is an example: > > [CCode (gir_namespace="GXml", gir_version="1.0")] > namespace GXml { > [CCode (gir_namespace="GXml", gir_version="1.0")] > namespace Dom { > public class Node : GLib.Object { > public void foo() { > stdout.printf("Node.foo()\n"); > } > } > > public class Attr : Node { > public new void foo () { > stdout.printf("Attr.foo()"); > } > } > } > } > _______________________________________________ > vala-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/vala-list >
_______________________________________________ vala-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/vala-list
