|
From: Nicholas N. <nj...@ca...> - 2003-10-21 09:24:46
|
On Tue, 21 Oct 2003, Olly Betts wrote: > > 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. Hmm, the docs are very vague about what 'maintainer-only' rules are. But I don't imagine we're using them. Thanks for the info. N |