GNOME Bugzilla – Bug 587601
Get rid of shave with AM_SILENT_RULES automake option
Last modified: 2009-08-16 19:32:48 UTC
automake1.11 has a feature that do the same as shave do. IMO would be better to "require newer version of existing tool" than to drag in a new special-purpose widget. Also, automake1.11 has already been added to gnome-autogen.sh The default build behavior is "same as previous" (i.e., verbose), but now user can choose quiet by "./configure --enable-silent-rules" or "make V=0". Alternately, AM_SILENT_RULES([yes]) makes quiet the default (same default as shave), and user can "./configure --disable-silent-rules" or "make V=1" to override. A hard dependency on automake 1.11 is not necessary. Only add m4_ifdef([AM_SILENT_RULES],[AM_SILENT_RULES([yes])]) to your configure.ac and should work and still be compatible with earlier automake versions. More info here: http://live.gnome.org/GnomeGoals/NicerBuilds and bug #580062
Created attachment 137729 [details] [review] Get rid of shave with AM_SILENT_RULES automake option
We could even support both shave for am <= 1.10 and the new thing for 1.11, I think: m4_ifdef([AM_SILENT_RULES], [AM_SILENT_RULES([yes])], [SHAVE_INIT([],[enable]) AC_CONFIG_FILES([shave shave-libtool])]) (untested, but ought to work)
Created attachment 138273 [details] [review] Use AM_SILENT_RULES if automake >= 1.11 is installed Thank you Christian for the tip!
I think we also need to sprinkle some $(AM_V_GEN) around, e.g. when generating the marshalers, etc. Plus, I think we should default to "no", not "yes".
Fixed in master. I left shave support in for now; we can always get rid of it later.