[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [automake] Dependency question with _LDADD

From: Braden McDaniel
Subject: Re: [automake] Dependency question with _LDADD
Date: Wed, 27 Aug 2008 14:45:56 -0400
User-agent: Thunderbird (Macintosh/20080707)

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 <address@hidden> - Tue, 26 Aug 2008 17:43:13 +0200
Why '-I config -I m4'?  AFAICS you do not use AC_CONFIG_MACRO_DIR([m4])
in  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

to the toplevel
... 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: <address@hidden>
<>               Jabber: <address@hidden>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]