From: Dave B. <da...@ff...> - 2004-01-23 17:13:38
|
On Fri, Jan 23, 2004 at 08:43:13AM -0800, Paul Mineiro wrote: > On Thu, 22 Jan 2004, Michael Radford wrote: > > > Ah, well of course, one way to avoid this problem is to not cut and > > paste AM_MAINTAINER_MODE into your configure.ac in the first place, so > > the automatic re-automake/autoconf rules are generated by default. :) > > > > So never mind.... Maybe I will add a note in the docs warning that > > AM_MAINTAINER_MODE is a bad idea in wigwam projects. > > well, wait, i (might) disagree. > > it's a question of how smart the maintainer mode is, wrt if a different > version of automake/autoconf is installed on the box than the one > "intended" to bootstrap the project. i don't know enough about that > magic "missing" script that automake uses ... but not enabling maintainer > mode seems safest in, e.g., a publish situation. > > so chris' suggestion of installing automake/autoconf into the project if > you're gonna regen configure seems appropriate. i think there's some confusion... by default, configure will include rebuild rules that don't require, but will use, the autotools. AM_MAINTAINER_MODE() changes it to not use locally installed tools by default, but with manually specifying --enable-maintainer-mode then the tools become required. Therefore, use AM_MAINTAINER_MODE() if you plan on checking in configure. If you plan on adding the autotools to your project then I guess you can either omit AM_MAINTAINER_MODE() or include project_configure_flags=--enable-maintainer-mode (And this latter is actually the suggestion I prefer at the moment) - dave |