| commit | 9b789bbdb594d08c581e385928a729eb670a6301 | [log] [tgz] |
|---|---|---|
| author | android-build-team Robot <android-build-team-robot@google.com> | Mon Nov 11 21:14:39 2019 +0000 |
| committer | android-build-team Robot <android-build-team-robot@google.com> | Mon Nov 11 21:14:39 2019 +0000 |
| tree | e5c856e4cb7f1d0b1161c1f0c151dac848b7fd85 | |
| parent | a3a9dec14cd9265df9abf9c61b13e24d5f1263d6 [diff] | |
| parent | afb0ff8fea3d8cfa6c44f7d7b62a4f71d62a88da [diff] |
Snap for 6001391 from afb0ff8fea3d8cfa6c44f7d7b62a4f71d62a88da to qt-aml-resolv-release Change-Id: Ife33beccd903b7a0124e86f57f538a2f60ce6c8a
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.