tag | dbf9bd4fb7268dc9fccf67c34520c40f11f6571c | |
---|---|---|
tagger | The Android Open Source Project <initial-contribution@android.com> | Fri May 31 15:55:23 2019 -0700 |
object | 79585c7fc8792d3ae492a9e3ec8509d42f575c2f |
Android 9.0.0 release 41
commit | 79585c7fc8792d3ae492a9e3ec8509d42f575c2f | [log] [tgz] |
---|---|---|
author | android-build-team Robot <android-build-team-robot@google.com> | Fri May 17 22:30:01 2019 +0000 |
committer | android-build-team Robot <android-build-team-robot@google.com> | Fri May 17 22:30:03 2019 +0000 |
tree | e0c7230d6defe3e36413f3cc83b0886a47ac8283 | |
parent | 02169b55afdedb85984cc9b0d6ac4b5463619bdc [diff] |
Version bump to PQ3A.190605.004.A1 [core/build_id.mk] Change-Id: Iee725a3fca0dc65b703296852a4b1dd1af5471d4
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.