tech-toolchain archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Per-shell override of path names in make(1)




To: tech-toolchain%netbsd.org@localhost

Subject: Re: Per-shell override of path names in make(1)

From: "Simon J. Gerraty" <sjg%crufty.net@localhost>

Date: Thu, 07 Feb 2008 16:12:41 -0800


>> > The SHELL make/env variable lets you set the shell make should use for
>> > all its commands.  This can to be a full path.

Actually make should not pay attention to $SHELL at all.
Imagine the hell that would result - trying to write a makefile that
would be usable by more than one person (think [t]csh vs [k]sh).

Here's a useful example of what you can do today without recompiling
anything:

.SHELL: name=sh path=/bin/bash

all:
        @echo "SHELL=$$SHELL BASH=$$BASH_VERSION"

$ make -f ~/tmp/make-tests/shell
SHELL=/bin/ksh BASH=2.05b.0(1)-release
$



References:

Re: Per-shell override of path names in make(1)
From: David Laight




Prev by Date: Re: Per-shell override of path names in make(1)

Next by Date: Re: Per-shell override of path names in make(1)

Previous by Thread: Re: Per-shell override of path names in make(1)

Next by Thread: Re: Per-shell override of path names in make(1)

Indexes:

reverse Date

reverse Thread

Old Index



Home | Main Index | Thread Index | Old Index