On 07/03/2012 10:54 PM, Stefano Lattarini wrote:
On 07/02/2012 02:57 PM, Stefano Lattarini wrote:
On 07/02/2012 02:26 PM, Ralf Corsepius wrote:
On 06/30/2012 08:30 PM, Stefano Lattarini wrote:
Maintaining ACLOCAL_AMFLAGS in the Makefile.am to pass extra flags
to aclocal is (and have always
On 07/04/2012 11:03 AM, Ralf Corsepius wrote:
On 07/03/2012 10:54 PM, Stefano Lattarini wrote:
On 07/02/2012 02:57 PM, Stefano Lattarini wrote:
On 07/02/2012 02:26 PM, Ralf Corsepius wrote:
ACLOCAL_AMFLAGS is able to take sequences of -I's.
Will your AC_CONFIG_MACRO_DIR be able handle such
[Adding bug-autoconf]
Reference:
http://lists.gnu.org/archive/html/automake-patches/2012-07/msg00011.html
On 07/04/2012 11:23 AM, Stefano Lattarini wrote:
On 07/04/2012 11:03 AM, Ralf Corsepius wrote:
Please revert this change.
No. Have you read my plan above? If the use case of multiple
See commit 'v1.12.1-165-gcd1a9cc' aclocal: deprecate ACLOCAL_AMFLAGS,
trace AC_CONFIG_MACRO_DIR instead in the Automake git repository.
See also follow-up discussion at:
http://lists.gnu.org/archive/html/automake-patches/2012-07/msg00010.html
* doc/autoconf.texi (@node Input @defmac
On 07/04/2012 04:55 AM, Stefano Lattarini wrote:
This will allow projects to use several m4 macro local dirs. This is
especially important for projects that are used as nested subpackages
of larger projects.
See also:
http://lists.gnu.org/archive/html/autoconf/2011-12/msg00037.html
On 07/04/2012 05:03 AM, Eric Blake wrote:
Would it also make sense to allow multiple calls to AC_CONFIG_MACRO_DIR
to stack, as in:
AC_CONFIG_MACRO_DIR([dir1])
AC_CONFIG_MACRO_DIR([dir2])
And should we mention that the first directory listed has special
significance to other tools like
On 07/04/2012 01:03 PM, Eric Blake wrote:
On 07/04/2012 04:55 AM, Stefano Lattarini wrote:
This will allow projects to use several m4 macro local dirs. This is
especially important for projects that are used as nested subpackages
of larger projects.
See also:
On 07/04/2012 01:28 PM, Eric Blake wrote:
On 07/04/2012 05:03 AM, Eric Blake wrote:
Would it also make sense to allow multiple calls to AC_CONFIG_MACRO_DIR
to stack, as in:
AC_CONFIG_MACRO_DIR([dir1])
AC_CONFIG_MACRO_DIR([dir2])
And should we mention that the first directory listed has
For master.
Stefano Lattarini (2):
aclocal: multiple local m4 macro dirs with AC_CONFIG_MACRO_DIR
aclocal: diagnose non-existing directories in AC_CONFIG_MACRO_DIR better
aclocal.in | 58 +-
t/aclocal-macrodir.tap | 158
It can be done either passing several arguments to a single invocation:
AC_CONFIG_MACRO_DIR([dir1 dir2])
or issuing more invocations:
AC_CONFIG_MACRO_DIR([dir1])
AC_CONFIG_MACRO_DIR([dir2])
This will allow projects to use several m4 macro local dirs. This is
especially important
This new implementation ensures that any directory (possibly excluding
the first one, if the '--install' option is used) that is declared with
AC_CONFIG_MACRO_DIR and that is non-existent will cause an error from
aclocal.
* aclocal.in (scan_m4_dirs): Add a new argument, telling whether it's OK
On 07/04/2012 09:24 AM, Stefano Lattarini wrote:
It can be done either passing several arguments to a single invocation:
AC_CONFIG_MACRO_DIR([dir1 dir2])
I would recommend against this,
or issuing more invocations:
AC_CONFIG_MACRO_DIR([dir1])
AC_CONFIG_MACRO_DIR([dir2])
Hi Eric.
On 07/04/2012 06:42 PM, Eric Blake wrote:
On 07/04/2012 09:24 AM, Stefano Lattarini wrote:
It can be done either passing several arguments to a single invocation:
AC_CONFIG_MACRO_DIR([dir1 dir2])
I would recommend against this,
or issuing more invocations:
13 matches
Mail list logo