| commit | 888d143e4c57c81634df7166b8fc86e00f38d7d7 | [log] [tgz] |
|---|---|---|
| author | Chih-Hung Hsieh <chh@google.com> | Mon Dec 09 19:32:03 2019 -0800 |
| committer | Chih-Hung Hsieh <chh@google.com> | Tue Dec 17 15:12:31 2019 -0800 |
| tree | ed01484eb15411116cd53d8cab8f0e9c600f261d | |
| parent | 20d1b7d9664990192a52dbf2dd6a3d7ee4123a9b [diff] |
Split warn.py into multiple files * Split warning patterns into *_warn_patterns.py * Split project list into android_project_list.py * Split out the Severity class, to be changed later * Split core of warn.py into warn_common.py and leave only platform dependent code in warn.py. This allows the core logic be used with different parallel processing libraries. * Old warn.py just calls -m warn.warn. Test: path_to_build/tools/warn.py build.log Test: warn.py --url=http://cs/android --separator='?l=' build.log > warnings.html Change-Id: I6734e4472a21018cd5ce06d549f6dbca24f4de54
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.