all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Package version at build side
Date: Tue, 04 Nov 2014 22:45:43 +0100	[thread overview]
Message-ID: <87vbmu7i7s.fsf@gnu.org> (raw)
In-Reply-To: <20141104193524.GA5700@debian> (Andreas Enge's message of "Tue, 4 Nov 2014 20:35:24 +0100")

Andreas Enge <andreas@enge.fr> skribis:

> for kdelibs, I need to pass the version of the input docbook-xsl as
> a configure flag. So I added something like
>
>        #:configure-flags
>         (list "-DCMAKE_VERBOSE_MAKEFILE=ON" ; for debugging
>               (let ((docbook-xsl (assoc-ref %build-inputs "docbook-xsl")))
>                 (string-append "-DDOCBOOKXSL_DIR="
>                                docbook-xsl
>                                "/xml/xsl/docbook-xsl-"
>                                (package-version docbook-xsl)
                                 ^
Missing unquote (comma) here.  --’
See gps.scm for an example.

> Now package-version seems to be defined in (guix package); when I add this as
> modules, more and more of them are pulled in. Currently I have
>
>        #:modules ((guix packages) ; for PACKAGE-VERSION
>                   (guix base32)
>                   (guix config)
>                   (guix derivations)
>                   (guix records)
>                   (guix serialization)
>                   (guix store)
>                   (guix utils)
>                   (guix build syscalls)
>                   (guix build utils))

The raison d’être of the (guix build …) name space is precisely to
distinguish modules to be used on the build side from modules to be used
on the host side (info "(guix) G-Expressions").  The above approach is
not going to work, because it tries to import purely host code on the
build side.

Thanks,
Ludo’.

      parent reply	other threads:[~2014-11-04 21:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-04 19:35 Package version at build side Andreas Enge
2014-11-04 20:55 ` Eric Bavier
2014-11-04 21:25   ` Andreas Enge
2014-11-04 21:45 ` Ludovic Courtès [this message]

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=87vbmu7i7s.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=andreas@enge.fr \
    --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.