Re: vpath / Re: ../configure question

[Troy Cauble]

Guido Draheim wrote:
> Es schrieb Guido Draheim:
>
> > Es schrieb Troy Cauble:

> > > In the middle of this large autoconf based project
> > > there's a third party module that does not use autoconf.
> > > "./configure" style builds work because make just finds
> > > the stock Makefile in the source directory.  "../configure"
> > > style builds break because autoconf didn't create a
> > > directory and Makefile in the $(top_builddir) tree.
> > >
> > > Is there a standard way to work around this other than
> > > adding Makefile.am's to the third party module?

> forgot: if you assume good vpath (in a corporate
> controlled environment that is a valid assumption)
> then you could have the copy-makefile-to-builddir
> done by autoconf itself - just rename the Makefile 
> to Makefile.in and include it into configure-output. 
> autoconf makes a copy for trying to substitute
> some at-vars where there are none - which still works.

That's the hint I needed.
Rename Makefile to Makefile.in, add address@hidden@,
and I'm done!

Thanks,
-troy