tag | 2502b84362d3a0dae2c101d2245ad76500964b22 | |
---|---|---|
tagger | The Android Open Source Project <initial-contribution@android.com> | Wed Oct 26 18:44:34 2022 -0700 |
object | b03fb089c66d65f5a664ca8ade9c39b13bdb6ec2 |
aml_tet_331012080
commit | b03fb089c66d65f5a664ca8ade9c39b13bdb6ec2 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Wed Sep 21 03:30:35 2022 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Wed Sep 21 03:30:36 2022 +0000 |
tree | bf1f956ec236dedb81db4fb68e40d74e1d6e1c14 | |
parent | 14a0fe20cc46a4d8d4e589c9f3b958eeb680ef75 [diff] |
Version bump to aml_tet_331012080 [core/build_id.mk] Change-Id: I3ad2b388429b3db4f38a7b6540d652dd8bf7a211
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.