| commit | bbaa5efbbc08202172806b7e89525635358f836b | [log] [tgz] |
|---|---|---|
| author | tyiu <tyiu@google.com> | Fri Oct 27 00:08:32 2023 +0000 |
| committer | Timothy Yiu <tyiu@google.com> | Mon Nov 27 19:29:31 2023 +0000 |
| tree | a030393b880eec1175843811be18dae832730ae3 | |
| parent | a997e4800012fd8b43775116730a42d54a99bd09 [diff] |
Add config for FULL_SYSTEM_OPTIMIZE_JAVA FULL_SYSTEM_OPTIMIZE_JAVA allows device to enable full system java optimization. Bug: 300514883 Test: local m Change-Id: Iba0a546ef2b721b929b791c6a9e6c854e9bec909 Merged-In: Iba0a546ef2b721b929b791c6a9e6c854e9bec909
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.