unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Raghav Gururajan <rg@raghavgururajan.name>
To: Julien Lepiller <julien@lepiller.eu>, help-guix@gnu.org
Subject: Re: Custom 'install phase
Date: Mon, 8 Mar 2021 03:16:20 -0500	[thread overview]
Message-ID: <c7a1a05d-2aac-e059-7d2d-bec852d7c8c8@raghavgururajan.name> (raw)
In-Reply-To: <D19DC5B5-80D9-4B7F-92C3-4A68562E80D9@lepiller.eu>


[-- Attachment #1.1: Type: text/plain, Size: 1458 bytes --]

Hi Julien!

> I think you need to remove the apply, but keep one level of parenthesis, 
> like so:
> 
> ((assoc-ref …) args …)
> 
> Apply takes the last arguments, which must be a list and appends all its 
> elements to the invocation. Like (apply foo '(1 2 3 4)) is tge same as 
> (foo 1 2 3 4). Here you're probably confused because of the assoc-ref is 
> not a procodure, but it's fine: it returns a procedure, so guile can 
> execute it and pass arguments to it the normal way.

So I tried the following:

```
            (replace 'install
              (lambda _
                (for-each (lambda (solution)
                            (with-directory-excursion solution
                                 ((assoc-ref copy:%standard-phases 'install)
                                        #:install-plan
                                        '(("src" (string-append 
"include/" solution)
                                           #:include-regexp ("\\.h$"))))))
                          (list
                           "qtlockedfile"
                           "qtpropertybrowser"
                           "qtservice"
                           "qtsingleapplication"
                           "qtsoap"))
                #t))
```

I get "In procedure string-append: Wrong type (expecting string): #f", 
with and without replacing `(string-append "include/" solution)` with 
`"include"`.

Regards,
RG.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

  reply	other threads:[~2021-03-08  8:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-07 19:06 Custom 'install phase Raghav Gururajan
2021-03-07 21:44 ` Julien Lepiller
2021-03-08  8:16   ` Raghav Gururajan [this message]
2021-03-08  9:26     ` Ricardo Wurmus
2021-03-08  9:35       ` Raghav Gururajan
2021-03-08 11:45         ` Julien Lepiller
2021-03-09  1:09           ` Raghav Gururajan
2021-03-09  2:37             ` Julien Lepiller
2021-03-09  3:28               ` Raghav Gururajan
2021-03-09  3:47                 ` Raghav Gururajan
2021-03-09  8:13             ` Ricardo Wurmus
2021-03-09  8:25               ` Raghav Gururajan

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=c7a1a05d-2aac-e059-7d2d-bec852d7c8c8@raghavgururajan.name \
    --to=rg@raghavgururajan.name \
    --cc=help-guix@gnu.org \
    --cc=julien@lepiller.eu \
    /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.
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).