[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: aclocal flags are a pain
From: |
Ralf Wildenhues |
Subject: |
Re: aclocal flags are a pain |
Date: |
Tue, 16 Sep 2008 23:37:49 +0200 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
Hello again,
* Behdad Esfahbod wrote on Tue, Sep 16, 2008 at 01:40:41AM CEST:
> To use an m4/ dir one has to modify three places:
>
> * autogen.sh: add "-I m4" to their aclocal invocation (ok, I know autoreconf
> prolly handles it),
Yes, it does. What keeps you from using it?
> * configure.ac: add AC_CONFIG_MACRO_DIR(m4)
>
> * Makefile.am: add ACLOCAL_AMFLAGS = -I m4
Again, flexibility: for example gcc in its tree has things like
ACLOCAL_AMFLAGS = -I ../config -I .. -I .
but its AC_CONFIG_MACRO_DIR is empty in some directories, and m4 or
../config in others.
> This makes no sense. aclocal should scan configure.ac and pick up the flags,
> and automake should use the configure.ac stuff to generate the correct aclocal
> rerun rule.
Hmmyes, this sounds like a better default than what we have now.
After all, a user that needs to override it can still set
ACLOCAL_AMFLAGS =
Lemme think about this one.
Thanks,
Ralf
- aclocal flags are a pain, Behdad Esfahbod, 2008/09/15
- Re: aclocal flags are a pain,
Ralf Wildenhues <=
- Re: aclocal flags are a pain, Behdad Esfahbod, 2008/09/16
- Re: aclocal flags are a pain, Behdad Esfahbod, 2008/09/17
- Re: aclocal flags are a pain, Ralf Wildenhues, 2008/09/17
- Re: aclocal flags are a pain, Behdad Esfahbod, 2008/09/17
- Re: aclocal flags are a pain, Ralf Wildenhues, 2008/09/17
- Re: aclocal flags are a pain, Behdad Esfahbod, 2008/09/17