> From: "Christian Jullien"
> Cc:
> Date: Thu, 23 Jan 2020 21:07:26 +0100
>
> Perhaps my sample was too simple.
> If I supply a Makefile that can work with or without sh.exe presence (on any
> user machines) I must rely on what make knows about the shell.
I'm saying such strategy is not the bes
> From: "Christian Jullien"
> Date: Thu, 23 Jan 2020 20:18:17 +0100
>
> Hum I see! It only a problem if I want to execute something if a sh.exe
> exists.
>
> search:
> ifeq ($(SHELL),sh.exe)
> grep something file
> else
> find "something" file
> endif
If you want to depend on the va
-Original Message-
From: Eli Zaretskii [mailto:e...@gnu.org]
Sent: Thursday, January 23, 2020 20:26
To: jull...@eligis.com
Cc: make-w32@gnu.org
Subject: Re: Why SHELL defaults to sh.exe
> From: "Christian Jullien"
> Date: Thu, 23 Jan 2020 20:18:17 +0100
>
> Hum I see! I
> From: "Christian Jullien"
> Cc:
> Date: Thu, 23 Jan 2020 15:54:50 +0100
>
> cmd>type Makefile
> all:
> @echo $(SHELL)
> cmd>.\gnumake
> sh.exe<=== Argl!!
Why is that a problem?
If you do
.\gnumake -f-
all:
dir *c
^Z
does it not invoke cmd.exe's DIR command? It do
> From: "Christian Jullien"
> Date: Thu, 23 Jan 2020 11:27:53 +0100
>
> I wonder why Windows native gnumake.exe defaults to sh.exe ?
Historical reasons.
> Building gnumake.exe with build_w32.bat (which defaults to cl.exe) still uses
> sh.exe while IMHO it should
> default to cmd.exe
It only d
d>type Makefile
all:
@echo $(SHELL)
cmd>.\gnumake
sh.exe<=== Argl!!
-Original Message-
From: Eli Zaretskii [mailto:e...@gnu.org]
Sent: Thursday, January 23, 2020 15:33
To: jull...@eligis.com
Cc: make-w32@gnu.org
Subject: Re: Why SHELL defaults to sh.exe
> From: &
Hi team,
I wonder why Windows native gnumake.exe defaults to sh.exe ?
Building gnumake.exe with build_w32.bat (which defaults to cl.exe) still
uses sh.exe while IMHO it should default to cmd.exe
In an ideal world, I should be able to get for example all .c source files
with:
FILES =
