commit | f535a00c39b45939733c9d9b63e1e9011ae82226 | [log] [tgz] |
---|---|---|
author | Duy Truong <duytruong@google.com> | Fri Jan 20 09:38:58 2023 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Fri Jan 20 09:38:58 2023 +0000 |
tree | 903dbe97c2f53cdd553378d5fa005ac2f19e4344 | |
parent | dff3b7e2101df9b99cfa485354da38cc7ab52ee5 [diff] | |
parent | f318e46c60a526b3032df4269e2bca4996236138 [diff] |
Merge "Include JDK with STS SDK like the other *TS suites." into sc-dev am: f318e46c60 Original change: https://googleplex-android-review.googlesource.com/c/platform/build/+/20950851 Change-Id: I003a446eb35ca0180ecdd0df6155caf600c3da9f 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.