tag | 08b095d4423b4851255c525397c16e0da6f391f8 | |
---|---|---|
tagger | The Android Open Source Project <initial-contribution@android.com> | Tue Jun 20 10:08:57 2023 -0700 |
object | f23125da2cca0653cae692e7e437b0ae1662d8b7 |
Android 13.0.0 release 55
commit | f23125da2cca0653cae692e7e437b0ae1662d8b7 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Fri Mar 10 05:10:03 2023 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Fri Mar 10 05:10:04 2023 +0000 |
tree | 3905022a0153cd04f5eed1a4b31f2fe761799a8b | |
parent | 96d864032002a73e8d32c811c6fb3e0f99338722 [diff] |
Version bump to TD2A.230203.028 [core/build_id.mk] Change-Id: I60f8cefeed6c1e1168d6324b37b6bf9bece8bc61
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.