Ralf Wildenhues wrote:
Hi Braden,
* Braden McDaniel wrote on Wed, Aug 27, 2008 at 08:48:45AM CEST:
On Wed, 2008-08-27 at 07:41 +0200, Ralf Wildenhues wrote:
* Michel Briand wrote on Wed, Aug 27, 2008 at 03:19:24AM CEST:
Ralf Wildenhues <[EMAIL PROTECTED]> - Tue, 26 Aug 2008 17:43:13 +0200
Why '-I config -I m4'? AFAICS you do not use AC_CONFIG_MACRO_DIR([m4])
in configure.ac. I'd use that, and drop '-I config'.
I do not use the macro you mention.
Please do, though. When you do, please also add
ACLOCAL_AMFLAGS = -I m4
to the toplevel Makefile.am.
... which brings up a question I have: Why doesn't AC_CONFIG_MACRO_DIR
eliminate the need for setting ACLOCAL_AMFLAGS as such?
Hmm. You typically have one AC_CONFIG_MACRO_DIR where for example
'aclocal --install' or 'libtoolize --install' will dump macro files.
However, you can have several places in the tree where you need to
pick up macro files from, with -I paths.
Fair enough; but most don't have more than one such directory. As a
result, having to point the autotools at this directory in more than one
place feels redundant.
Is there a reason not to give aclocal invocations a -I flag for the
AC_CONFIG_MACRO_DIR? ACLOCAL_AMFLAGS could complement this.
--
Braden McDaniel e-mail: <[EMAIL PROTECTED]>
<http://endoframe.com> Jabber: <[EMAIL PROTECTED]>
