all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: Guix-devel <guix-devel@gnu.org>
Subject: Re: Dealing with language bindings for libraries.
Date: Wed, 9 May 2018 20:00:00 +0200	[thread overview]
Message-ID: <20180509200000.70057cca@lepiller.eu> (raw)
In-Reply-To: <59b27dad-ef1d-54ea-3b7b-ae6d437e3b2b@fastmail.net>

Le Wed, 9 May 2018 18:25:13 +0200,
Konrad Hinsen <konrad.hinsen@fastmail.net> a écrit :

> On 09/05/2018 17:21, Fis Trivial wrote:
> 
> > An ideal scenario would be the one that we can specify multiple
> > outputs for one packages, each output corresponds to one language
> > binding, and we can specify different dependencies and build system
> > for each output. Is there any chance we can do that in guix?  
> 
> +1
> 
> I am currently in exactly the same situation.
> 
> Konrad.

We already have such a case: capstone and python-capstone. There is no
redundancy since python-capstone knows how to load the shared library
created in the capstone package. So we have two packages, with the same
build time as with one package, but much easier to create. The only
difficulty is to make the binding find the library (but the same would
be true for different outputs I guess).

HTH

  reply	other threads:[~2018-05-09 18:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-09 15:21 Dealing with language bindings for libraries Fis Trivial
2018-05-09 16:25 ` Konrad Hinsen
2018-05-09 18:00   ` Julien Lepiller [this message]
2018-05-11  5:49     ` Konrad Hinsen
2018-05-09 18:45 ` Ricardo Wurmus
2018-05-09 19:33   ` Fis Trivial
2018-05-09 20:08     ` Ricardo Wurmus
2018-05-10  5:02       ` Fis Trivial
2018-05-10  8:18 ` Catonano
2018-05-10  9:27   ` Fis Trivial
2018-05-10 15:08     ` Catonano

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=20180509200000.70057cca@lepiller.eu \
    --to=julien@lepiller.eu \
    --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.