On 09/15/2010 04:37 AM, langdead wrote:
Hi, I want to ask a question. Whether does "ACLOCAL_AMFLAGS= -I @path" only work for "Makefile.am"?
In the context of autoreconf (the only part of the equation belonging to autoconf), we merely call aclocal without grepping for ACLOCAL_AMFLAGS, so it does not matter to autoreconf what file (if any) contains that line. It is all up to aclocal where that line is located, but aclocal belongs to the automake project, therefore, this is a question better asked on the automake lists.
The GDAL project combines both autotools and ordinary makefile mechanism. And it use another template file 'GDALmake.opt.in' instead of 'Makefile.am'. When I extend this library, I can't use autoreconf to update the 'configure' file to contain my own *.m4 file, because the ACLOCAL_AMFLAGS is not passed to aclocal by autoreconf. And autoreconf can't receive the parameter "-I @path" as its help document said either.
Did you literally mean '-I @path', or were you intending '-I @path@' or '-I $(path)'?
-- Eric Blake ebl...@redhat.com +1-801-349-2682 Libvirt virtualization library http://libvirt.org
