Re: Why gmake create two path environment variables

> Date: Mon, 20 Oct 2008 17:48:26 -0400
> From: Soren Andersen <[email protected]>
> 
> > And second, this feature is not for the shell specifically
> > (although if your shell is a port of a Unixy shell, it will want
> > PATH), it is for _any_ program that wants PATH.  Let me remind
> > you that Make will invoke programs directly, not through the
> > shell, whenever it can (i.e. when the rule's command does not use
> > any characters special to the shell, like redirection and pipes).
> Actually, this is incorrect. There is no such thing as "invoke[ing]
> programs directly" on MS Windows operating systems. All invocations
> go through the CMD processor.

I meant "directly" in a sense that the program is called by a direct
call to CreateProcess, rather than calling it through "cmd /c" or (if
a Unixy shell is found) "sh -c".

> IMHO Activeperl and GNU-make for Win32 are both distinctly wrong to
> handle ENV %vars% in this (case-sensitive) manner.

GNU Make doesn't.  It just does a service to other programs that might
do so.