|
From: Olly B. <ol...@su...> - 2003-10-21 10:06:32
|
On Tue, Oct 21, 2003 at 09:28:35AM +0100, Nicholas Nethercote wrote:
> Ah, so automake can rerun itself when necessary? That would be great...
> is it just a matter of not specifying AM_MAINTAINER_MODE?
Yes and yes.
> What's the advantage of having AM_MAINTAINER_MODE?
Here's what the automake docs say:
`AM_MAINTAINER_MODE'
This macro adds a `--enable-maintainer-mode' option to
`configure'. If this is used, `automake' will cause
`maintainer-only' rules to be turned off by default in the
generated `Makefile.in's. This macro is disallowed in `Gnits'
mode (*note Gnits::). This macro defines the `MAINTAINER_MODE'
conditional, which you can use in your own `Makefile.am'.
I think the idea is to turn off extra rules and dependencies which aren't
useful to people who are only building the software, and would be confused
if they managed to invoke them. But then it confuses people like me not to
regenerate when configure.in or a Makefile.am is modified!
Since valgrind is aimed squarely at developers, AM_MAINTAINER_MODE seems of
little benefit.
Or if you'd prefer to leave AM_MAINTAINER_MODE in, you can turn maintainer
mode back on for yourself by configuring with:
configure --enable-maintainer-mode
Cheers,
Olly
|