commit | 1a4f65c33f5a13d51bcd4f7bb22a0d5c0bd8364c | [log] [tgz] |
---|---|---|
author | Anton Hansson <hansson@google.com> | Thu May 26 16:43:53 2022 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Thu May 26 16:43:53 2022 +0000 |
tree | f938be62dd3e10d6fac91a2032e55ff7efb7312c | |
parent | efe6f9a6841955335b9745045bc19d56fb44882a [diff] | |
parent | e59bd2aa7c70511611d4a54138b655dbbdf4eb2a [diff] |
Merge changes from topic "sdk-refactor-tmd" into tm-dev am: e59bd2aa7c Original change: https://googleplex-android-review.googlesource.com/c/platform/build/+/18598732 Change-Id: I7af2aa8a57bf4b3f6b6bd27f983802c8c3874d1c Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
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.