From: Stefano Lattarini Date: Fri, 15 Jun 2012 08:09:04 +0000 (+0200) Subject: Merge branch 'silent-custom' into maint X-Git-Tag: v1.12.2~75 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=401a2a82c602f24ed82ce95b2a48cf786198e42d;p=thirdparty%2Fautomake.git Merge branch 'silent-custom' into maint * silent-custom: silent: new $(AM_V_P) variable, tell if we're running in silent mode refactor: silent rules handling (a little) refactor: &define_verbose_var: accept a third optional argument Signed-off-by: Stefano Lattarini --- 401a2a82c602f24ed82ce95b2a48cf786198e42d diff --cc NEWS index b61d58ad2,bced15f26..347287e1c --- a/NEWS +++ b/NEWS @@@ -60,22 -60,12 +60,28 @@@ New in 1.12.2 input file. Such a warning will also be present in the next Autoconf version (2.70). +* Cleaning rules: + + - Recursive cleaning rules descends into the $(SUBDIRS) in the natural + order (as done by the other recursive rules), rather than in the + inverse order. They used to do that in order to work a round a + limitation in an older implementation of the automatic dependency + tracking support, but that limitation had been lifted years ago + already, when the automatic dependency tracking based on side-effects + of compilation had been introduced. + + - Cleaning rules for compiled objects (both "plain" and libtool) work + better when subdir objects are involved, not triggering a distinct + 'rm' invocation for each such object. They do so by removing *any* + compiled object file that is in the same directory of a subdir + object. See automake bug#10697. + + * Silent rules support: + + - A new predefined $(AM_V_P) make variable is provided; it expands + to a shell conditional that can be used in recipes to know whether + make is being run in silent or verbose mode. + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ New in 1.12.1: