commit | 63c2db4d3b4ec5fd10ed920e32171e0ce190a66b | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Wed Feb 15 00:00:39 2023 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Wed Feb 15 00:59:14 2023 +0000 |
tree | 79a31defc076fcb624e96e55f826f85c868eacff | |
parent | 7200856928f08f33c537e52d46f39738e8d5d336 [diff] | |
parent | 033f4d10953451d40c41aeaaeaaf4433054b0322 [diff] |
Make change and version bump to TQ3A.230215.001 Snap for 9606726 from 033f4d10953451d40c41aeaaeaaf4433054b0322 to tm-qpr3-release Change-Id: Id79bff6a5b781f5b7c192edc33774b3d700b5a33
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.