commit | 5ae55196616a2f714d3dc073e694af3a55e66ed7 | [log] [tgz] |
---|---|---|
author | Chih-Hung Hsieh <chh@google.com> | Mon Feb 24 10:20:36 2020 -0800 |
committer | Chih-Hung Hsieh <chh@google.com> | Tue Feb 25 19:47:35 2020 -0800 |
tree | a9501c41b154fb796329d8adab078303ddedaaa0 | |
parent | b5aad1b937c465f7c6ffbb7d37ae79a20574b27d [diff] |
Use same warn_common.py and warn.py for Android and Chrome * add chrome_project_list.py * use newer Chrome's warn_common.py and severity.py * modify warn_common.py to work with both python2 and python3, to work with and without google3 Test: warn.py --url=http://cs/android --separator='?l=' build.log > warnings.html Test: warn.py --gencsv build.log > warnings.csv Change-Id: I9aeee7031c11988d8ead1733ff4846ae6cb1ee73
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.