unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Craven <david@craven.ch>
To: ng0 <ng0@libertad.pw>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: rust: cargo build-system: how to handle libraries
Date: Wed, 28 Dec 2016 10:59:20 +0100	[thread overview]
Message-ID: <CAL1_im=9U7Nb=Hn=B0X-9MAnAd+xTgMp20=1L=4H40wK0POZeg@mail.gmail.com> (raw)
In-Reply-To: <87bmvws8tf.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me>

> Of course I meant Cargo.lock, not Cargo.toml ... so I know what I
> have to search for, and this makes it a bit easier than the
> previous search.

See cargo workspaces:
https://github.com/rust-lang/libc/blob/master/Cargo.toml
https://github.com/rust-lang/rfcs/blob/master/text/1525-cargo-workspace.md

It's a fairly new thing, you'll have to track down the relevant
commits in cargo and check if the cargo version we are using is new
enough and understand it's semantics and how it applies to the cargo
build system.

My recommendation to fix this issue is to not run the tests if there
isn't a Cargo.lock file, but this is likely not going to solve the
underlying cause in this case. You can also package version 0.2.16
which does not use workspaces.

  reply	other threads:[~2016-12-28  9:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-27 23:57 rust: cargo build-system: how to handle libraries ng0
2016-12-28  0:07 ` David Craven
2016-12-28  9:24   ` ng0
2016-12-28  9:26     ` ng0
2016-12-28  9:59       ` David Craven [this message]
2016-12-28 16:42         ` ng0
2016-12-28 16:49           ` 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

  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='CAL1_im=9U7Nb=Hn=B0X-9MAnAd+xTgMp20=1L=4H40wK0POZeg@mail.gmail.com' \
    --to=david@craven.ch \
    --cc=guix-devel@gnu.org \
    --cc=ng0@libertad.pw \
    /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).