On Tue, Oct 20, 2009 at 16:02:15 +0100, Gordon Allott wrote:
> Hi all,
>
> So the general background of this is that I am building bindings for a
> library that depends on GdkPixbuf, instead of using vala-gen-introspect
> i am using gobject-introspection to build a gir file and build a vapi
> from that. However there is a conflict between the GdkPixbuf gir file
> and the GdkPixbuf vapi file.
>
> Essentially gir's namespace is
> GdkPixbuf
> and vala's namespace is:
> Gdk with a class Pixbuf
Because of gir's file == namespace == library gir can't do otherwise, while
vala can reopen namespaces however it wants, so it chooses a more convenient
way. You probably want to use the existing .vapi for compatibility.
> which is right? the GdkPixbuf gir file is automatically generated, but
> then again it does not contain any classes.
For vala, the .vapi is right, I believe.
> The end result of this is that vala can not find the namespace GdkPixbuf
> in its vapi files because obvious, it does not exist
>
> anyone have any clues? is gir at fault or vala? I have attached both the
> gir and vapi files in question to this email so you don't have to go dig
> them out
I think you should be able to move the symbols to different names and
namespaces at vapigen stage using the .metadata just like you would with
vapi-gen-introspect (which is basically an old version of g-ir-scanner using
older gobject-introspection format). But I didn't do it myself, so I can't
tell you more details. Have a look at the existing .metadata files (in
vapi/packages in the vala source tree) and try it out.
--
Jan 'Bulb' Hudec <b...@ucw.cz>
_______________________________________________
Vala-list mailing list
Vala-list@gnome.org
http://mail.gnome.org/mailman/listinfo/vala-list
