The user still has full control over verbosity levels, both setting
their per-project defaults at configure time (or even in a config.site
file), as well as a per-run override. But these days, most projects
are defaulting to silent rules.

* configure.ac (AM_SILENT_RULES): Add, to match what most projects
are doing these days.

Signed-off-by: Eric Blake <[email protected]>
---
 ChangeLog    | 4 ++++
 configure.ac | 1 +
 2 files changed, 5 insertions(+)

diff --git a/ChangeLog b/ChangeLog
index e063f94..26998b5 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,9 @@
 2016-12-31  Eric Blake  <[email protected]>

+       maint: make silent builds the default
+       * configure.ac (AM_SILENT_RULES): Add, to match what most projects
+       are doing these days.
+
        maint: release no longer creates a diff file
        * HACKING: Drop outdated steps.

diff --git a/configure.ac b/configure.ac
index 6793087..78b8788 100644
--- a/configure.ac
+++ b/configure.ac
@@ -24,6 +24,7 @@ AC_CONFIG_AUX_DIR([build-aux])

 AM_INIT_AUTOMAKE([1.11.6 dist-bzip2 dist-xz color-tests parallel-tests
 silent-rules subdir-objects gnu])
+AM_SILENT_RULES([yes]) # make --enable-silent-rules the default.

 m4_pattern_forbid([^M4_[A-Z]])

-- 
2.9.3


_______________________________________________
M4-patches mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/m4-patches

Reply via email to