After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 655653 - Add GObject introspection support
Add GObject introspection support
Status: RESOLVED DUPLICATE of bug 655651
Product: gcr
Classification: Core
Component: gck
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GNOME keyring maintainer(s)
GNOME keyring maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2011-07-30 20:00 UTC by Evan Nemerson
Modified: 2019-03-23 21:19 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gck: add GObject introspection support (1.80 KB, patch)
2011-07-30 20:01 UTC, Evan Nemerson
none Details | Review
gck: add GObject introspection support (1.77 KB, patch)
2011-08-04 04:22 UTC, Evan Nemerson
none Details | Review

Description Evan Nemerson 2011-07-30 20:00:53 UTC
GCK is currently missing gobject-introspection support.
Comment 1 Evan Nemerson 2011-07-30 20:01:43 UTC
Created attachment 192923 [details] [review]
gck: add GObject introspection support
Comment 2 Stef Walter 2011-08-01 12:37:16 UTC
I get this message when trying to build this bug:

gck/Makefile.am:81: HAVE_INTROSPECTION does not appear in AM_CONDITIONAL
Comment 3 Stef Walter 2011-08-01 12:37:44 UTC
I mean 'build this attachment'
Comment 4 Evan Nemerson 2011-08-04 04:22:02 UTC
Created attachment 193225 [details] [review]
gck: add GObject introspection support

Interesting... I wonder why it works here. Regardless, it's not really necessary.

This removes the HAVE_INTROSPECTION conditional. Note that this depends on the change made to configure.in by patch in bug #655651.
Comment 5 Stef Walter 2011-08-11 20:42:47 UTC
Since this is an ongoing bit of work (until we get all the warnings and gtk-doc bits figured out), let's work on this in bug #655651 together with the gcr introspection stuff.

*** This bug has been marked as a duplicate of bug 655651 ***