GNOME Bugzilla – Bug 655651
Add GObject introspection support
Last modified: 2019-02-22 11:59:30 UTC
GCR needs a GIR
Created attachment 192920 [details] [review] gcr: add GObject introspection support
Created attachment 192921 [details] [review] gcr: add GObject introspection support Slightly modified version to add Gcr-3.0.gir and Gcr-3.0.typelib to .gitignore
Created attachment 192922 [details] [review] gcr: mark many fields as private This will mark some stuff in the API as private.
Created attachment 193208 [details] [review] gcr: add GObject introspection support Remove the HAVE_INTROSPECTION conditional.
Created attachment 193224 [details] [review] gcr: add GObject introspection support Instead of using Gcr-@GCR_MAJOR@-@GCR-MINOR@.gir for the name of the GIR, use Gcr-@GCR_MAJOR@-@GCR-MINOR@.gir. This is *probably* more appropriate (unless there are API breaks between minor versions).
Thanks for working on this. Really great! At the desktop summit, I joined in on the gobject introspection hackfest and worked on this a bit. I committed your patches to a branch: http://git.gnome.org/browse/gnome-keyring/log/?h=introspection And added quite a few patches as well. I was mostly offline at the time, so I had a hard time updating this bug. I don't think we should merge this until we have pretty much most of the g-ir-scanner warnings taken care of. That means: * Fixing bugs in gobject-introspection (I've already gotten two bug fixes merged at the hackfest) * Fixing the gtk doc comments in libgcr and libgck. In order to do this, I think we should track both the gcr and gck additions in a single bug. So I'll close the other one and track here. Did I get all your changes in that branch?
*** Bug 655653 has been marked as a duplicate of this bug. ***
Merged into gnome-keyring master.