diff options
author | Michael Adam <obnox@samba.org> | 2009-09-22 13:09:25 +0200 |
---|---|---|
committer | Michael Adam <obnox@samba.org> | 2009-09-22 13:09:25 +0200 |
commit | 50c781d0c9dd991b2af14e41ccfaafbb04be48d7 (patch) | |
tree | 10620d1a6ce6db8d0867fe1773aa11b0b4d813b1 /tests/scripts/run_tests_valgrind.sh | |
parent | e8cbd7088c29d46c71f9f89bf9afbdb3c9ef6648 (diff) | |
download | tinyproxy-50c781d0c9dd991b2af14e41ccfaafbb04be48d7.tar.gz tinyproxy-50c781d0c9dd991b2af14e41ccfaafbb04be48d7.zip |
build: import the AM_SILENT_RULES if available, but default to verbose.
Automake 1.11 (and I think 1.10b already) offers the AM_SILENT_RULES macro.
This adds switches --quiet, --enable-silent-rules and --disable-silent-rules
to configure.
--quiet makes the configure run itself quite.
--enable-silent-rules makes the compile process less verbose:
for a file that is compiled without errors or warnings, a simple
"CC main.o" is printed (e.g.). Compiler warnings and errors
are printed of course.
This makes it much easier (IMHO) to spot build problems.
--disable-silent-rules turns the silent rules off
I have set it up such that the default for tinyproxy is to build
in verbose mode (i.e. with silent rules disabled). This prints
the whole compile call command line for each source file compiled,
precisely as before.
You can also control verbose/non-verbose mode at "make" time, i.e.
after configure has run, by calling "make V=0 ..." or "make V=1 ..."
for running in silent and verbose mode, respectively.
If the version automake used to create configure is too old,
the result is unaltered, compared to the result before this change.
Wow - this is a long commit message for a 1-liner.
But since I discussed this with Mukund earlier, and he did
not seem to be too fond if this, I felt the need to justify
this change... :-)
Michael
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions