tag | 874da84f14121c977dd0aa5ba5040318fad7f4a0 | |
---|---|---|
tagger | The Android Open Source Project <initial-contribution@android.com> | Mon May 06 14:11:14 2019 -0700 |
object | 9f4db7673b2bf2bdcfd76c58cceca3eac2c0c622 |
Android 9.0.0 Release 37 (PQ3A.190505.002)
commit | 9f4db7673b2bf2bdcfd76c58cceca3eac2c0c622 | [log] [tgz] |
---|---|---|
author | android-build-team Robot <android-build-team-robot@google.com> | Tue Apr 09 14:10:07 2019 +0000 |
committer | android-build-team Robot <android-build-team-robot@google.com> | Tue Apr 09 14:10:09 2019 +0000 |
tree | 1e84ae6fa7a75e0c0c7ca945df131a6cbc877871 | |
parent | e8a051499a6908241c73a2b5095bce1fda3f869c [diff] |
Version bump to PQ3A.190505.002 Change-Id: If7c2b20298260c8909fa87ec4bb8dbe43f632ed9
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.