| commit | d591a5e01208693f3273a5327a1568ebd4c109a8 | [log] [tgz] |
|---|---|---|
| author | Chih-Hung Hsieh <chh@google.com> | Tue Sep 24 11:13:00 2019 -0700 |
| committer | Chih-Hung Hsieh <chh@google.com> | Tue Sep 24 14:52:09 2019 -0700 |
| tree | 864a033b0aa5020ffb522cb1fa18d304cd42d8e2 | |
| parent | 465946c5a83e6e5136d14e9bc34581a1f06c607a [diff] |
Add new compiler warning patterns * Add Kotlin, NDK, Protoc, Asm, and other new patterns. * Put all clang-analyzer warnings to the ANALYZER severity group. Some security and null pointer warnings still have HIGH severity. * Comment out old C/C++ warnings that overlap with analyzer warnings and do not appear in current build.log. * Other old fixed warning patterns should be commented out later. Bug: 141493530 Test: warn.py --url=http://cs/android --separator='?l=' build.log > warnings.html Change-Id: Idc7b09e5e4eefa127d41e9f37da1f566ed1ede1f
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.