GNOME Bugzilla – Bug 615518
Add m4/introspection.m4 so that gobject-introspection is not required when building from git.
Last modified: 2018-05-24 12:13:08 UTC
Created attachment 158478 [details] [review] Add m4/introspection.m4 so that gobject-introspection is not required when building from git. Similar to what is done in e.g. gtk+.
I don't like the idea of doing this: it means we'd have to keep it up-to-date, which is really not something that will happen. What's the issue with having gobject-introspection when you build from git?
(In reply to comment #1) > I don't like the idea of doing this: it means we'd have to keep it up-to-date, > which is really not something that will happen. > > What's the issue with having gobject-introspection when you build from git? In the ARM Linux Internet Platform we build filesystems for embedded devices from git. I don't want to install gobject-introspection on the target only for getting introspection.m4. Adding m4/introspection.m4 is what e.g. gtk+ and atk do. The alternative would be to move introspection.m4 to glib.
Re-assigning to glib. It all boils down to the question whether building GNOME or parts of GNOME from git without installing gobject-introspection should be supported, and if yes, how to provide introspection.m4. I'd personally prefer having it supported by moving introspection.m4 to glib, and if that's considered OK I can provide a patch. For the record, software currently shipping a copy of introspection.m4 in git includes: - atk - clutter - gstreamer - gtk+ - unique
General GLib bug, moving over from introspection.
Yes, let's put introspection.m4 in glib.
*** Bug 623492 has been marked as a duplicate of this bug. ***
This bug has been open for 8 months. Can the error message at least be made more useful, as I requested in bug 638936? "HAVE_INTROSPECTION does not appear in AM_CONDITIONAL" is not the best indicator that I need to install the gobject-introspection package.
*** Bug 640630 has been marked as a duplicate of this bug. ***
*** Bug 633065 has been marked as a duplicate of this bug. ***
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/glib/issues/284.