commit | cb69c6f22daa463c4793c8b68c56aefd4b10ab84 | [log] [tgz] |
---|---|---|
author | Shintaro Kawamura <kawasin@google.com> | Thu Mar 06 16:36:52 2025 +0900 |
committer | Shintaro Kawamura <kawasin@google.com> | Mon Mar 10 10:55:22 2025 +0900 |
tree | bd478f2576a75e6ad191cdeae5660771c32aee8f | |
parent | 67acd19ec51b62b4cb6f5531f5ef7bd3d7224395 [diff] |
Include init-mmd-prop.rc if mmd is not built The build flag RELEASE_MEMORY_MANAGEMENT_DAEMON will be eventually enabled. If mmd is not built into the image, init-mmd-prop.rc sets "mmd.enabled_aconfig" sysprop to unblock swapon_all execution. Devices launching mmd in Trunkfood and Nextfood are supposed to execute swapon_all command on "on property:mmd.enabled_aconfig=*" trigger. On devices with mmd enabled, we need `mmd.enabled_aconfig` sysprop to be empty by default, to let swapon_all command wait until aconfig flag value is loaded to the system property. Bug: 393481329 Test: manual Change-Id: I9082b30fd3fac51e079587d4de4cf92d55f7fccc
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.