unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: guix-devel@gnu.org, David Craven <david@craven.ch>
Subject: Re: cargo-build-system: cargo-build-flags: --cfg=unix in package recipe
Date: Tue, 3 Jan 2017 02:46:39 +0100	[thread overview]
Message-ID: <20170103024639.12e685ab@scratchpost.org> (raw)
In-Reply-To: <20170103021018.64ac3887@scratchpost.org>

It was missing in guix/build-system/cargo.scm cargo-build as a keyword parameter.

Adding

 (define* (cargo-build store name inputs
                       #:key
                       (tests? #t)
                       (test-target #f)
-                      (configure-flags #f)
+                      (configure-flags #f) ; XXX unused
+                      (cargo-build-flags ''("--release"))
                       (phases '(@ (guix build cargo-build-system)
                                   %standard-phases))
                       (outputs '("out"))
@@ -89,6 +99,7 @@ to NAME and VERSION."
                                  source))
                     #:system ,system
                     #:test-target ,test-target
+                    #:cargo-build-flags ,cargo-build-flags
                     #:tests? ,tests?

makes it work.

  reply	other threads:[~2017-01-03  1:46 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 [this message]
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
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

  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=20170103024639.12e685ab@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=david@craven.ch \
    --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 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).