commit | 84b485a456b62752022827bb9f67c9e0684b076c | [log] [tgz] |
---|---|---|
author | Jeongik Cha <jeongik@google.com> | Fri Apr 12 09:00:37 2024 +0000 |
committer | Gerrit Code Review <noreply-gerritcodereview@google.com> | Fri Apr 12 09:00:37 2024 +0000 |
tree | 15c2af197b5592f348db7978e3d6d0edde91ca28 | |
parent | 5d09b51ba9f273dfaf467c3308ad4e60c5475072 [diff] |
Revert^2 "Expose RELEASE_AVF_SUPPORT_CUSTOM_VM_WITH_PARAVIRTUALIZED_DEVICES" This reverts commit 5d09b51ba9f273dfaf467c3308ad4e60c5475072. Reason for revert: relanding Change-Id: I537ec04c5c89c8d0d8abeb17f0c2c9cb13a3cfae
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.