Re: AC_CONFIG_MACRO_DIR vs m4_include

[Brandon Invergo]

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

-- 
Brandon Invergo
http://brandon.invergo.net

pgp29nclAuyzK.pgp
Description: PGP signature