all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Craven <david@craven.ch>
To: ng0 <ng0@we.make.ritual.n0.is>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH v2] gnu: Add rust (sidenotes on rust)
Date: Tue, 13 Sep 2016 14:28:25 +0200	[thread overview]
Message-ID: <CAL1_imnHs1nL593j40U3FT=jAOnMVSxP786JCNYaz7ASVzmpJw@mail.gmail.com> (raw)
In-Reply-To: <8760q0dmau.fsf@we.make.ritual.n0.is>

> How problematic will this be for us? Our person in charge for the rust
> stuff works around this by including copies of the libraries in a folder
> named 'third_party', but I don't understand enough of the language and
> lack a build system at the moment.

Initially this isn't a problem, since we'll use cargo to build the c
dependencies of a package. The cargo packages that wrap c packages
usually have a detection mechanism to use system libraries instead of
building them - but I haven't looked into how this works exactly.

> These two links should be useful too, so it might not be that hard to
> establish a build system.

I don't think it's hard, but just takes time. The part that I expect
will take more time than the build system is the importer.

  reply	other threads:[~2016-09-13 12:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-07  5:57 [PATCH v2] gnu: Add rust Eric Le Bihan
2016-09-07  8:48 ` David Craven
2016-09-13 11:55   ` [PATCH v2] gnu: Add rust (sidenotes on rust) ng0
2016-09-13 12:19     ` ng0
2016-09-13 12:28       ` David Craven [this message]
2016-09-13 12:09 ` [PATCH v2] gnu: Add rust ng0
2016-09-13 17:20   ` Eric Le Bihan
2016-09-13 18:29     ` ng0
2016-09-13 18:45       ` ng0
2016-09-13 19:11         ` ng0

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='CAL1_imnHs1nL593j40U3FT=jAOnMVSxP786JCNYaz7ASVzmpJw@mail.gmail.com' \
    --to=david@craven.ch \
    --cc=guix-devel@gnu.org \
    --cc=ng0@we.make.ritual.n0.is \
    /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.