tag | 51c1074fa2923d1abf273ef9f40193238467e180 | |
---|---|---|
tagger | The Android Open Source Project <initial-contribution@android.com> | Thu Nov 10 21:08:42 2022 -0800 |
object | 9424f99d9c9d7190833598b829e4408b4a07b682 |
aml_tz3_312410020
commit | 9424f99d9c9d7190833598b829e4408b4a07b682 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Mon Nov 07 11:44:59 2022 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Mon Nov 07 11:45:01 2022 +0000 |
tree | 0e5d7f485295a9d168700e839f5343a540721df5 | |
parent | 118bfd2fc377a3296d5ff025859db32d48b1cc18 [diff] |
Version bump to aml_tz3_312410020 [core/build_id.mk] Change-Id: I40103d6f64cdba212aee68dd080fd0dad26afb7e
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.