commit | 6375b6d7306e4804c31cab05e63ac28e17ef2e36 | [log] [tgz] |
---|---|---|
author | Chih-Hung Hsieh <chh@google.com> | Fri Dec 15 15:41:14 2017 -0800 |
committer | Chih-Hung Hsieh <chh@google.com> | Fri Dec 15 15:41:14 2017 -0800 |
tree | 2f2611293b97f572d079b74e36e02e5d0d665521 | |
parent | 4b7ab33f4e1dde9ed10a648d8e516c097d5aaaa3 [diff] |
Call clang-tidy with -quiet unless WITH_TIDY is set. * Default builds calls clang-tidy only if enabled locally. In this case, clang-tidy should be quiet. * If WITH_TIDY is 1 or true, let clang-tidy emit default messages. * Even with -quiet and all warnings are suppressed, clang-tidy emits one line message of the number of suppressed messages. This one-liner could be suppressed in future changes. Bug: 69051430 Test: default build and build with WITH_TIDY=1 Change-Id: I3138ef45fc4372f904787bd1a391e8d88050f0b3
This is the Makefile-based portion of the Android Build System.
For documentation on how to run a build, see Usage.txt
For a list of behavioral changes useful for Android.mk writers see Changes.md
For an outdated reference on Android.mk files, see build-system.html. Our Android.mk files look similar, but are entirely different from the Android.mk files used by the NDK build system. When searching for documentation elsewhere, ensure that it is for the platform build system -- most are not.
This Makefile-based system is in the process of being replaced with Soong, a new build system written in Go. During the transition, all of these makefiles are read by Kati, and generate a ninja file instead of being executed directly. That's combined with a ninja file read by Soong so that the build graph of the two systems can be combined and run as one.