commit | 2819a5beedfd7c3c261da783daeb2842581a8433 | [log] [tgz] |
---|---|---|
author | Jared Duke <jdduke@google.com> | Thu Nov 18 13:00:02 2021 -0800 |
committer | Jared Duke <jdduke@google.com> | Thu Dec 02 15:56:10 2021 -0800 |
tree | d14e74661b28897a4c78606f2ad0b975c29252cd | |
parent | 351cd2e48901d31fe2b070cf847608bd70ffe39a [diff] |
Add Soong variable for optimizing system Java Introduce a Soong variable to allow selective enabling of Java optimizations for platform targets. This will be used initially to control optimizations (and shrinking) for system server + sysui. Opting in to optimizations can be achieved with either: * Env: export SYSTEM_OPTIMIZE_JAVA=true * Make: $(call add_soong_config_var_value,ANDROID,SYSTEM_OPTIMIZE_JAVA,true) Note that the actual framework build rule changes to hook into this variable will land separately. Bug: 203088572 Test: `SYSTEM_OPTIMIZE_JAVA=true m` (observe env variable change log) Change-Id: I959985bdff394c2445cb1632116846a8d2f5443d
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.