%% Dan Jacobson <[EMAIL PROTECTED]> writes:
dj> In Info, one cannot find how to change PATH in a Makefile.
dj> PATH=/usr/sbin:$(PATH) won't do without spelling out PATH.
dj> The best one can do is once on each line:
dj> P=PATH=/usr/sbin:$$PATH
dj> a:
dj> $P; which faubackup
???
You
In Info, one cannot find how to change PATH in a Makefile.
PATH=/usr/sbin:$(PATH) won't do without spelling out PATH.
The best one can do is once on each line:
P=PATH=/usr/sbin:$$PATH
a:
$P; which faubackup
___
Bug-make mailing list
[EMAIL PROTE
Consider a Makefile that starts thus:
include ../../../Makefile-master
It would be nice if this included Makefile-master knew where it was, so it could do
stuff like this:
root := $(MAKEFILE-PARENT-DIR)
classesDir := $(root)/classes
I use this unsatisfactory workaround:
Makef
Boris Kolpackov wrote:
Alternatively, if you have a makefile which is always included at the
top (say your bootstrap.make file) you can put the "all" target in that
file as the first thing:
Now you are forcing user to use the same name for default target which is
not always acceptable (well, at lea
Paul D. Smith <[EMAIL PROTECTED]> writes:
> The way I typically solve this is that I always define the target I want
> to be the default first, with no prerequisites etc. Simply putting
> something like:
>
> all:
>
> by itself at the top of the first makefile is enough to force make to
> c
%% Boris Kolpackov <[EMAIL PROTECTED]> writes:
bk> I came to the point where I cannot work around "default target
bk> hijacking" problem. So I am planning to do something about it in
bk> my -bk patch-set. I also hope this feature will end up in the main
bk> stream thus this RFC.
bk> Whe
Good day,
I came to the point where I cannot work around "default target
hijacking" problem. So I am planning to do something about it
in my -bk patch-set. I also hope this feature will end up in the
main stream thus this RFC.
When makefile inclusion is used there is a recurring problem of
defau
