From: Wojtek Kosior via <help-guix@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Peter Polidoro <peter@polidoro.io>, "(" <paren@disroot.org>,
help-guix@gnu.org
Subject: Re: Using Makefile to run guix shell?
Date: Thu, 8 Dec 2022 22:30:48 +0100 [thread overview]
Message-ID: <20221208223048.00edc36c.koszko@koszko.org> (raw)
In-Reply-To: <86r0x9g2bx.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 682 bytes --]
> ifndef GUIX_ENVIRONMENT
> todo:=echo
> else
> todo:=hello
> endif
>
> stuff:
> @echo "Enter stuff"
> @echo "GUIX_ENVIRONMENT: ${GUIX_ENVIRONMENT}"
> $(todo)
> @echo "stuff done."
>
> hello:
> guix shell -C hello make -- $(MAKE) stuff
>
> .PHONY: stuff hello
>
> [...]
>
> Note that the Makefile calls the Makefile but since it is run inside a
> shell --container, then you need to provide ’make’.
>
>
> Cheers,
> simon
>
What is the purpose of using `$(MAKE)` over just `make` in the recipe
in this case? It would only be appropriate if you wanted the same make
to be used for both the manual and recursive invocation, right?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-12-08 21:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 14:47 Using Makefile to run guix shell? Peter Polidoro
2022-12-07 15:12 ` (
2022-12-07 15:26 ` Peter Polidoro
2022-12-07 15:38 ` (
2022-12-07 18:27 ` Peter Polidoro
2022-12-07 21:01 ` Wojtek Kosior via
2022-12-08 10:44 ` zimoun
2022-12-08 14:21 ` Peter Polidoro
2022-12-08 15:30 ` Wojtek Kosior via
2022-12-08 18:47 ` zimoun
2022-12-08 21:30 ` Wojtek Kosior via [this message]
2022-12-08 23:04 ` zimoun
2022-12-08 23:24 ` Wojtek Kosior via
2022-12-09 17:46 ` Peter Polidoro
2022-12-10 13:21 ` zimoun
2022-12-12 17:55 ` Peter Polidoro
2022-12-12 19:00 ` Wojtek Kosior via
2022-12-09 18:38 ` Philip McGrath
2022-12-07 17:08 ` Wolf
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=20221208223048.00edc36c.koszko@koszko.org \
--to=help-guix@gnu.org \
--cc=koszko@koszko.org \
--cc=paren@disroot.org \
--cc=peter@polidoro.io \
--cc=zimon.toutoune@gmail.com \
/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).