all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Craven <david@craven.ch>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: cargo-build-system: cargo-build-flags: --cfg=unix in package recipe
Date: Tue, 3 Jan 2017 11:57:48 +0100	[thread overview]
Message-ID: <CAL1_imniTUJzG1ApQ7WoqGAp9tU7SWfBKowE8p68iSQwaUEQwQ@mail.gmail.com> (raw)
In-Reply-To: <20170103033234.7d3573ec@scratchpost.org>

> Aha! It can - if one uses propagated-inputs in the package recipes. I think the importer should propagate inputs if the current package is Rust-source-only. Otherwise packages further down the dependency graph (further to the clients) won't compile later.

One of the ideas behind the [replace] stuff in the Cargo.toml file was
to retain the required dependencies.

> However, some of the Rust crates have a "windows" target which fails.
> For these I'd like to pass "--cfg=unix" and I'd like to put it into the package recipe and not hardcode it into the build system.

Nice, didn't know about this flag. That explains why it refused to
build without the windows dependencies.

  reply	other threads:[~2017-01-03 10:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-03  1:10 cargo-build-system: cargo-build-flags: --cfg=unix in package recipe Danny Milosavljevic
2017-01-03  1:46 ` Danny Milosavljevic
2017-01-03  2:32 ` Danny Milosavljevic
2017-01-03 10:57   ` David Craven [this message]
2017-01-03 11:55     ` Danny Milosavljevic
2017-01-04 11:38       ` ng0
2017-01-04 11:45         ` David Craven
2017-01-04 13:26           ` Danny Milosavljevic
2017-01-04 13:44             ` ng0
2017-01-03 20:10     ` Danny Milosavljevic
2017-01-03 11:19 ` ng0
2017-01-03 12:02   ` Danny Milosavljevic
2017-01-03 14:09     ` ng0
2017-01-03 14:38       ` David Craven

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_imniTUJzG1ApQ7WoqGAp9tU7SWfBKowE8p68iSQwaUEQwQ@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.