commit | fc94c5072171e68b7c4111427b181fc17bfdbc03 | [log] [tgz] |
---|---|---|
author | Sorin Basca <sorinbasca@google.com> | Thu Nov 24 10:12:49 2022 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Thu Nov 24 10:12:49 2022 +0000 |
tree | 4142a99115aac2fa9c25e55af4a8e01ddb50910c | |
parent | bd703c3fa3c39eb95ffba486bd3d5d2998863ad0 [diff] | |
parent | c87d15adb8246fde0e037047234cf2993acc89aa [diff] |
Merge "Fix Java flags in TF template to work with JDK 17+" am: c87d15adb8 Original change: https://android-review.googlesource.com/c/platform/build/+/2313308 Change-Id: Ib78c80b1afd59cdea17fcb3a9b5d240e09a86104 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.