| commit | 02f0df83fc1d389c189b8e1c7278cfdfa33c62bd | [log] [tgz] |
|---|---|---|
| author | Chih-Hung Hsieh <chh@google.com> | Thu Jan 20 16:13:12 2022 -0800 |
| committer | Chih-Hung Hsieh <chh@google.com> | Thu Jan 20 16:13:12 2022 -0800 |
| tree | 37175f82d4568fdb10a5fdfccfdd239a5ea1a57c | |
| parent | 89d7061ed3a2b6cf4f9b4fb735ddabc1477bf1ae [diff] |
Lower severity of 3 tidy warnings * bcmp/bcopy/bzero are not insecureAPI on Android. * Android projects may enable/disable clang-tidy checks locally; warn/*patterns.py keep global classification of all warnings. Test: warn.py --url=http://cs/android --separator='?l=' build.log > warnings.html Test: warn.py --gencsv build.log > warnings.csv Change-Id: I7720f7babd0a33c1b6602c9a8bb67565c45db94e
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.