Re: VPATH elimination by configure

[Ganesan Rajagopal]

>>>>> "Lars" == Lars J Aas <address@hidden> writes:

> On Wed, Jan 17, 2001 at 11:17:00AM +0100, Akim Demaille wrote:
> : It seems to me that Autoconf's job is not to remove unportable code
> : written by the user, so it seems wrong to have it remove VPATH
> : definitions from Makefiles.  Historically I'm sure it was useful, in a
> : previous century, in a previous millennium.  Today, I tend to think
> : automake should *warn* when it sees VPATH in a Makefile.am, and
> : autoconf should shut up and do nothing.
> : 
> : Comments?

> I'm all for this if the user can silence the warning by doing something
> with a variable setting in the Makefile.am in case he knows what he is
> doing.

I am curious which versions of automake actually remove VPATH. Is it only
the CVS version? I've been using VPATH without any problems with autoconf
2.13. I agree with Lars that there should be a way to silence these
warnings. I commonly use a statement like "VPATH=$(srcdir)" to make builds
possible in non-source directories.

Ganesan

-- 
R. Ganesan (address@hidden)       | Ph: 91-80-5721856 Ext: 2149
Novell India Development Center.       | #include <std_disclaimer.h>