* Jan Engelhardt wrote on Wed, Mar 11, 2009 at 09:34:20PM CET: > On Wednesday 2009-03-11 21:06, Ralf Wildenhues wrote: > > Do we want to allow a command line knob (--silent-rules) to turn > > off `silent' mode, or do we force developers to either touch the > > AUTOMAKE_OPTIONS variable in Makefile.am or the AM_INIT_AUTOMAKE > > macro call in configure.ac? > > Hm, what is the difference between silent and silent-rules?
The command line option --silent-rules does the same as the argument `silent' to the AM_INIT_AUTOMAKE macro in configure.ac: AM_INIT_AUTOMAKE([silent]) Both enable silent mode for all Makefile.in files. Per-Makefile.in silent mode may be enabled by adding AUTOMAKE_OPTIONS = silent to the respective Makefile.am. The reason that the command line option is not called `--silent' is that normally, i.e., with several other GNU software, --silent is the opposite of --verbose, and changes the verbosity of the command. But --silent-rules does not change the verbosity of the automake command. Hope that clears things up. Cheers, Ralf
