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
