unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Wojtek Kosior <koszko@koszko.org>
Cc: Peter Polidoro <peter@polidoro.io>, "(" <paren@disroot.org>,
	help-guix@gnu.org
Subject: Re: Using Makefile to run guix shell?
Date: Fri, 09 Dec 2022 00:04:17 +0100	[thread overview]
Message-ID: <86359pa45q.fsf@gmail.com> (raw)
In-Reply-To: <20221208223048.00edc36c.koszko@koszko.org>

Hi,

On Thu, 08 Dec 2022 at 22:30, Wojtek Kosior via <help-guix@gnu.org> wrote:

>> hello:
>> 	guix shell -C hello make -- $(MAKE) stuff

[...]

> 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?

No specific reason.  Initially I wrote without the container option ’-C’
or --pure, so really recursive.  But then I checked if it also worked
with the container option ’-C’ and let the old $(MAKE) invocation.

In case reader is not convinced, here $(MAKE) does not refer to the same
’make’:

--8<---------------cut here---------------start------------->8---
$ cat Makefile
stuff:
	which make

guixy:
	@guix shell -C which make -- $(MAKE) stuff

$ which make
/usr/bin/make

$ make stuff
which make
/usr/bin/make

$ make guixy
which make
/gnu/store/dp8bar2xgzwz1yfm9lcafqn3vhs2cjqc-profile/bin/make
--8<---------------cut here---------------end--------------->8---

Cheers,
simon


  reply	other threads:[~2022-12-08 23:04 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
2022-12-08 23:04                 ` zimoun [this message]
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=86359pa45q.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=koszko@koszko.org \
    --cc=paren@disroot.org \
    --cc=peter@polidoro.io \
    /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).