unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Federico Beffa <beffa@ieee.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: gobject-introspection typelibs and shared libraries
Date: Mon, 8 Dec 2014 13:21:20 +0100	[thread overview]
Message-ID: <CAKrPhPMgDOqu66aGkQMBin4ZFOnbwVcO_+kYaPYD5ur17pKNKA@mail.gmail.com> (raw)
In-Reply-To: <87k322cx77.fsf@gnu.org>

On Mon, Dec 8, 2014 at 10:22 AM, Ludovic Courtès <ludo@gnu.org> wrote:
> 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.

Actually, I see that this part of gobject-introspection was slightly
edited from our version 1.38.0 to later ones. Nix uses 1.40.0 and the
newest is 1.42.0. So I'm planning to upgrade to the latest.

> Do we also need to do something for GI_TYPELIB_PATH?  Perhaps this
> should be in the ‘native-search-paths’ field of gobject-introspection?

I think that we do not need to set GI_TYPELIB_PATH in
gobject-introspection, but in in the packages making use of it.

Fede

  reply	other threads:[~2014-12-08 12:21 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
2014-12-08 12:21       ` Federico Beffa [this message]
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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKrPhPMgDOqu66aGkQMBin4ZFOnbwVcO_+kYaPYD5ur17pKNKA@mail.gmail.com \
    --to=beffa@ieee.org \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).