|
From: | Eric Blake |
Subject: | Re: need to set ACLOCAL_AMFLAGS along with AC_CONFIG_MACRO_DIR |
Date: | Wed, 15 Sep 2010 14:11:17 -0600 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.9) Gecko/20100907 Fedora/3.1.3-1.fc13 Mnenhy/0.8.3 Thunderbird/3.1.3 |
[adding bug-automake] On 09/15/2010 12:59 PM, Ralf Wildenhues wrote:
Hello, * Eric Blake wrote on Wed, Sep 15, 2010 at 04:15:13PM CEST:On 09/15/2010 04:37 AM, langdead wrote: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,That's not true. autoreconf.in:autoreconf_current_directory greps for /^ACLOCAL_[A-Z_]*FLAGS\s*=\s*(.*)/
Ah - I missed the regex (I was searching for a literal ACLOCAL_AMFLAGS, and didn't realize that it would be hidden behind a regex). Thanks for correcting me.
so it really only works with autoreconf to put literal stuff in that line. When aclocal is run from make, as triggered by the automake-generated rule, $(ACLOCAL_AMFLAGS) undergoes usual make expansion of course.
At any rate, it seems like maintaining ACLOCAL_AMFLAGS in Makefile.am is redundant - how hard is it to teach automake to have aclocal _automatically_ include directories mentioned inside AC_CONFIG_MACRO_DIR, to avoid the dual file maintenance headache?
-- Eric Blake address@hidden +1-801-349-2682 Libvirt virtualization library http://libvirt.org
[Prev in Thread] | Current Thread | [Next in Thread] |