tag | f1b33468f0a3dd2ba5966585c54ddbfa8539197d | |
---|---|---|
tagger | The Android Open Source Project <initial-contribution@android.com> | Mon May 01 15:42:09 2023 -0700 |
object | 6dea012a9e810a7c3acb3df9f6ed9f741e52f347 |
Android security 11.0.0 release 67
commit | 6dea012a9e810a7c3acb3df9f6ed9f741e52f347 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Mon Apr 03 15:55:10 2023 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Mon Apr 03 15:55:12 2023 +0000 |
tree | e5c3eb8c4871f31c146747f86eb31ec572e9cc14 | |
parent | b330965e765b4525452413eb472c45c072c4c920 [diff] |
Version bump to RSV1.210329.089 [core/build_id.mk] Change-Id: Ibd4dff2d6e2e6dd15803f8a42e6652556ce7e702
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.