| commit | 27a04f57038c86f3fdfbe2998123578dc3ee69a5 | [log] [tgz] |
|---|---|---|
| author | T.J. Mercier <tjmercier@google.com> | Fri Jan 03 18:25:04 2025 +0000 |
| committer | T.J. Mercier <tjmercier@google.com> | Fri Jan 03 18:25:54 2025 +0000 |
| tree | 1fe3cf9ec2d2c9354de0a0ddf14904934a70c146 | |
| parent | e56edd1c1e7ad4b49f1385db00d4edb7c400705e [diff] |
Remove PRODUCT_MEMCG_V2_FORCE_ENABLED
Commit 18a5d3920a ("Add flags for cgroup v2 and memcg v2 features")
added a build flag that allows forcing the memory cgroup controller to
v2 when PRODUCT_MEMCG_V2_FORCE_ENABLED is true. However the memory
controller is now v2 by default since commit 5fa48a84b
("libprocessgroup: memcg default version 1 -> 2") so this build flag is
no longer needed.
Bug: 327480673
Bug: 377579705
Change-Id: I770efa71d8f57abee58adc2be4bac097d35e3b34
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.