From: David Craven <david@craven.ch>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: rust: Crate Dependencies
Date: Thu, 29 Dec 2016 12:35:37 +0100 [thread overview]
Message-ID: <CAL1_im=HCh4mRY7FSD0PtxSQGMj2VyiEQMJYOmXg6VZCXBpiUg@mail.gmail.com> (raw)
In-Reply-To: <20161229121255.750fa1e3@scratchpost.org>
Hi Danny,
> How does rustc find the (Rust) dependencies when building a package in cargo-build-system?
You should be able to override the default rust or cargo version by
passing #:rustc or/and #:cargo as arguments to the build-system. See
guix/build-system/cargo.scm.
> I read that there are actual Rust binary libraries, seldomly used, and everything-included-only-as-source otherwise. How do I specify which it is?
By actual Rust binary library I assume you mean a library with a C ABI
that can be dynamically linked against, written in rust.
A library like that should or would contain a Cargo.lock file nailing
down all the crate versions required, making sure that the project can
be built using the same rustc and cargo versions.
With a Cargo.lock file present the only remaining issue is figuring
out whether it can be built with the rustc release or if it requires
features from beta/nightly.
I don't know a specific example of one, but I also read that it is
possible. I think that the cargo install should take care of
installing such a library, but I don't think it's implemented yet.
HTH!
next prev parent reply other threads:[~2016-12-29 11:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-28 14:51 rust: Crate Dependencies Danny Milosavljevic
2016-12-29 10:49 ` David Craven
2016-12-29 11:12 ` Danny Milosavljevic
2016-12-29 11:35 ` David Craven [this message]
2016-12-29 12:33 ` ng0
2016-12-29 17:35 ` David Craven
2016-12-29 20:10 ` 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_im=HCh4mRY7FSD0PtxSQGMj2VyiEQMJYOmXg6VZCXBpiUg@mail.gmail.com' \
--to=david@craven.ch \
--cc=dannym@scratchpost.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.