From: ng0 <ng0@libertad.pw>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: cargo-build-system: cargo-build-flags: --cfg=unix in package recipe
Date: Tue, 03 Jan 2017 11:19:55 +0000 [thread overview]
Message-ID: <8737h0wftw.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20170103021018.64ac3887@scratchpost.org>
Danny Milosavljevic <dannym@scratchpost.org> writes:
> Hi,
>
> so it seems I got the cargo-build-system to work for large-ish Rust dependency trees now. It still can't pick up transitive dependencies but hey :P
>
> 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.
>
> I saw that there's a "cargo-build-flags" parameter. However, specifying it like
>
> (arguments
> `(#:cargo-build-flags '("--cfg=unix" "--release")))
>
> gives me "invalid keyword argument"...
>
> Why?
>
>
It does indeed, and this would fix the bug I filed.
I've cut down the number of crates I packaged from 160 to 81 just
by removing the *32-sys and winapi dependencies after reading a
bit about the system.
--
♥Ⓐ ng0
PGP keys and more: https://n0is.noblogs.org/ http://ng0.chaosnet.org
next prev parent reply other threads:[~2017-01-03 11:20 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
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 [this message]
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=8737h0wftw.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me \
--to=ng0@libertad.pw \
--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.