Expose whether ashmem allocations are allowed Devices with vendor API level 202604 or higher will not allow ashmem allocation for applications that target SDK version 37 or higher. Restricting ashmem allocations as such and using memfd instead will allow memfd to completely replace ashmem once all supported devices have a vendor API level of 202604 or higher, and applications all target SDK version 37 or higher. Expose a boolean that communicates if a device meets this criteria to soong, so that the sepolicy generation logic can use this variable. Bug: 443130838 Change-Id: I5e0e987e754370d8772c6f2ab581d4dd5740736d Signed-off-by: Isaac J. Manjarres <isaacmanjarres@google.com>
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.