[Top][All Lists]

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

Re: AC_CONFIG_MACRO_DIR vs m4_include

From: Brandon Invergo
Subject: Re: AC_CONFIG_MACRO_DIR vs m4_include
Date: Wed, 21 Aug 2013 00:19:50 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)

Nick Bowler <address@hidden> writes:

> Despite documentation to the contrary, until recently (and not in the
> tool versions you are using), AC_CONFIG_MACRO_DIR never actually did
> anything at all.  For this reason alone, I strongly recommend not
> specifying it.

OK, good to know.  Thanks!

> Since you say you are using Automake (although your snippet above does
> not include an AM_INIT_AUTOMAKE call, I assume this is an oversight),

Sorry, I only mentioned Automake because it provides aclocal.  Automake
itself isn't actually being used in this case.

> Regardless, aclocal's functionality should not be confused with
> m4_include.  The latter is a core feature of the Autoconf language,
> whereas aclocal is just a tool to automatically generate an aclocal.m4
> file which
>   (a) copies the relevant Automake macros into your project, and
>   (b) includes (using m4_include) your local project macros based on
>       some loose text matching.
> Hope that helps,

Yep, makes sense.  I'll just go ahead with m4_include then.

Thanks again for your help!


Brandon Invergo

Attachment: pgpCN3TqOu1Dx.pgp
Description: PGP signature

reply via email to

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