On Thu, 2014-05-15 at 15:15 +0200, Milan Crha wrote:
On Thu, 2014-05-15 at 11:13 +0100, Philip Withnall wrote:If you have some output showing the errors gobject-introspection gives you when you run it on libical, I might be able to help you fix them.Hi, we tried to "introspect" libical inside libecal, basically by boxing libical types. The mos common error (warning) is about "Unresolved type"-s. These involve icaltimezone and icalcomponent. Both types are really defined as incomplete [1], but also out of the eds source. This marks related functions as unintrospectable. Another issue is with enums. Also the naming is not what gobject-introspection likes, there is no camel-case naming used in libical. I suppose half of the problem would be to solved by generating gir files directly in libical, but I'm afraid it'll not be enough, due to those incomplete types (the enums might be fixed by this, I guess).
So Fabiano asked about this in #gnome-hackers yesterday, and I think the conclusion was to do something similar to what's done in Cairo: add the G_DEFINE_BOXED_TYPE and glib-mkenums boilerplate somewhere (either directly in libical, or in a small libical-glib library which otherwise does *not* wrap the libical API). I think gobject-introspection will need fixing to support non-standard names for APIs and types. Philip
Attachment:
signature.asc
Description: This is a digitally signed message part