commit | 7cefe70a0015aa728ebc3e38862ab00dc37f0a1e | [log] [tgz] |
---|---|---|
author | Jeongik Cha <jeongik@google.com> | Wed Apr 10 00:39:48 2024 +0900 |
committer | Jeongik Cha <jeongik@google.com> | Thu Apr 11 09:03:04 2024 +0000 |
tree | 15c2af197b5592f348db7978e3d6d0edde91ca28 | |
parent | cf7f5375be2fcda77c192a23ad84afeb9a7ce99c [diff] |
Expose RELEASE_AVF_SUPPORT_CUSTOM_VM_WITH_PARAVIRTUALIZED_DEVICES expose the flag to soong. the flag is to indicate a custom VM can use para-virtualized devices. Bug: 333495394 Test: build Change-Id: I4e1854b5701302ae0ec1bf73862f264642b6e418
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.