On Thu, Sep 16, 2010 at 6:11 AM, Eric Blake <[email protected]> wrote: > On 09/15/2010 12:59 PM, Ralf Wildenhues wrote: >> * 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?
If you do this, where will you specify the `--install` flag to aclocal? Still in ACLOCAL_AMFLAGS? -- Jack
