GNOME Bugzilla – Bug 577347
Define a standard pkgconfig variable to store the g-i name for a library
Last modified: 2018-02-08 11:49:46 UTC
We need to have a bijunction between pkgconfig and g-i gir|typelib for a library. The gir format already defines a <package/> tag to link to the pkgconfig file. We would need a pkgconfig variable to have the other way of the relationship. I would propose "gi-module:" but that may be another variable name.
Also, if we can't have nested namespace, then one may provide multiple gir files for a pkg. Thus, I propose: gi-modules: my-gir1.gir my-gir2.gir
I like the idea. gi-name: perhaps?
I'd say definitely omit the .gir extension, since it's also useful to lookup the the typelib. Also I'd prefer either gi-names or gi-namespaces since that's how it's referred to in the tools, API and docs right now.
Ok so we just need to pick something here...I think gi-namespaces is closest to the introspection terminology. Any objections or can I just go ahead and commit this to some modules?
I guess this is good enough. Will that be retrieved and handled through some APIs in GIRepository ?
(In reply to comment #5) > I guess this is good enough. Will that be retrieved and handled through some > APIs in GIRepository ? Is "pkg-config --variable=gi-namespaces gtk2" sufficient? I'm not aware of much precedent for APIs around pkg-config since it's used only at build time, and most build systems are designed around invoking subprocesses.
[Mass-moving gobject-introspection tickets to its own Bugzilla product - see bug 708029. Mass-filter your bugmail for this message: introspection20150207 ]
-- 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/gobject-introspection/issues/16.