| commit | 8af29d4ec054e9ffcd0e4b94febc88728517bd13 | [log] [tgz] |
|---|---|---|
| author | Jiyong Park <jiyong@google.com> | Tue Jun 23 16:46:38 2020 +0900 |
| committer | Jiyong Park <jiyong@google.com> | Tue Jun 30 14:28:25 2020 +0900 |
| tree | 2251ac7c35f4d6feaa59e706423fdf5e1b9b8500 | |
| parent | 7b933fb5763d09c4ba29d6587c0a45b5d4be56da [diff] |
pm.dexopt.* props in runtime_libart.mk becomes optional The mk file is designed to provide safe default values which can be overridden by target-specific mk files. Previously it was difficult to correctly configure the mk files because the final prop value that is baked in the system/build.prop is highly dependent (and sensitive as well) to the mk file inheritance order which is very difficult (and non-intuitive) to follow. I9c073a21c8257987cf2378012cadaeeeb698a4fb is an attempt to make it much easier and intuitive. Specifically, the new `a ?= b` syntax makes the assignment optional, which means it is used only when there is no non-optional assignment for the same prop regardless of the relative ordering among them. In addition, the change prohibits having multiple non-optional prop assignments for the same prop name. pm.dex.* prop in runtime_libart.mk are now set using the `a ?= b` syntax to explicitly mark that they provide default values. Bug: 117892318 Bug: 158735147 Test: m Exempt-From-Owner-Approval: cherry-pick from master Merged-In: I044486d313d699607cd54222ae34d9eae24762b9 (cherry picked from commit bca4ea477a7a7e854491e80b38fab9ebf621ce07) Change-Id: I044486d313d699607cd54222ae34d9eae24762b9
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.