Mail Archives: djgpp-workers/1999/02/23/10:51:33
Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:
> On Tue, 23 Feb 1999, Salvador Eduardo Tropea (SET) wrote:
>
> > Then make should process argv[0]. After all that's the normal case when
> > called from command line and not spawned.
>
> I would prefer to solve a local problem (i.e. backslashes mishandling in
> Makefile command lines) locally. This means that the function which
> interprets the command lines read from a Makefile should be changed to
> not strip the backslashes under some conditions, so that cases like what
> you reported would work.
>
> OTOH, what you suggest has a global effect (it changes how the value of
> $(MAKE) will look in recursive Make's) which could break something,
> somewhere. Who knows, maybe some Makefile out there writes the value of
> $(MAKE) to a file and expects it to be with backslashes?
[If I understood your explanation about command line call to make and make
spawned by make]
But if I call make from the command line it process argv[0] anyways!!
From my point of view if something breaks is already broken, at least fix
something that can be fixed.
$(MAKE) should be the same no matters if I call make from the command line or
if I spawn make (from make or other program).
If somebody spects $(MAKE) to have forward slashes s/he won't get it if make
is called from the command line.
SET
------------------------------------ 0 --------------------------------
Visit my home page: http://welcome.to/SetSoft
or
http://www.geocities.com/SiliconValley/Vista/6552/
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Alternative e-mail: set-soft AT usa DOT net set AT computer DOT org
ICQ: 2951574
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA
TE: +(5411) 4759 0013
- Raw text -