From: ludo@gnu.org (Ludovic Courtès)
To: Federico Beffa <beffa@ieee.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: gobject-introspection typelibs and shared libraries
Date: Mon, 08 Dec 2014 10:22:52 +0100 [thread overview]
Message-ID: <87k322cx77.fsf@gnu.org> (raw)
In-Reply-To: <CAKrPhPPmAzQA1o+kUgb=NDex_+1rbTkoYuzC9uO6Q9=d3R4+ag@mail.gmail.com> (Federico Beffa's message of "Sun, 7 Dec 2014 23:11:24 +0100")
Federico Beffa <beffa@ieee.org> skribis:
> On Sun, Dec 7, 2014 at 9:48 PM, Ludovic Courtès <ludo@gnu.org> wrote:
>> Federico Beffa <beffa@ieee.org> skribis:
>>
>>> currently the typelib files used by gobject-introspection can't find
>>> shared libraries and require setting LD_LIBRARY_PATH.
>>
>> I don’t know much about all this; could you give some context? What’s a
>> typelib files exactly?
>
> gobject-introspection is a tool to create bindings to C libraries for
> other languages. To make the system flexible it creates an
> intermediate object. typelib files are a binary store on disk of this
> intermediate object.
>
> https://developer.gnome.org/gi/stable/overview.html
OK.
> The problem I've found is that the typelib files include the name of
> required shared libraries (.so), but not the absolute path. Therefore
> I was forced to set the LD_LIBRARY_PATH.
Yes, I see in the diagram on the page above that libraries are actually
dlopened, with the name that appears in the typelib file.
Thus the patch you proposed is the right thing, I think. Before
committing, could you add a comment a the top of the file explaining
that the file names contained in typelib files are meant to be dlopen’d,
hence this patch? Also please credit the original author of the patch.
> I was actually googling to find out how to instruct an application
> where to look for the typelib files, when I saw this email
>
> http://lists.science.uu.nl/pipermail/nix-dev/2014-September/014309.html
>
> and thought that we could borrow the approach.
Definitely.
Do we also need to do something for GI_TYPELIB_PATH? Perhaps this
should be in the ‘native-search-paths’ field of gobject-introspection?
(It would be good to push both changes at once, if appropriate, to
reduce rebuilds.)
Thanks for the explanations, and for addressing this!
Ludo’.
next prev parent reply other threads:[~2014-12-08 9:23 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-07 14:21 gobject-introspection typelibs and shared libraries Federico Beffa
2014-12-07 20:48 ` Ludovic Courtès
2014-12-07 22:11 ` Federico Beffa
2014-12-08 9:22 ` Ludovic Courtès [this message]
2014-12-08 12:21 ` Federico Beffa
2014-12-08 14:51 ` Federico Beffa
2014-12-08 20:37 ` Ludovic Courtès
2014-12-09 19:30 ` Federico Beffa
2014-12-09 20:27 ` Federico Beffa
2014-12-10 4:15 ` Mark H Weaver
2014-12-09 20:58 ` Ludovic Courtès
2014-12-10 4:39 ` Mark H Weaver
2014-12-10 4:54 ` Mark H Weaver
2014-12-10 8:48 ` Ludovic Courtès
2014-12-10 8:57 ` Federico Beffa
2014-12-10 12:56 ` Ludovic Courtès
2014-12-16 19:45 ` Federico Beffa
2014-12-17 7:20 ` Mark H Weaver
2014-12-17 8:57 ` Ludovic Courtès
2015-01-13 17:10 ` Federico Beffa
2015-01-13 20:22 ` Ludovic Courtès
2015-01-13 21:40 ` Federico Beffa
2015-01-14 20:43 ` Ludovic Courtès
2015-01-15 8:27 ` Federico Beffa
2015-01-15 21:42 ` Ludovic Courtès
2015-01-16 17:07 ` Federico Beffa
2015-01-16 20:47 ` Andreas Enge
-- strict thread matches above, loose matches on Subject: below --
2015-01-17 9:46 Federico Beffa
2015-01-17 10:15 ` 宋文武
2015-01-17 12:02 ` Andreas Enge
2015-01-18 9:39 ` Federico Beffa
2015-01-18 13:16 ` Andreas Enge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k322cx77.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=beffa@ieee.org \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.