commit | 28a57dc1ccbfee86fbc09127ff05dea07f735d5f | [log] [tgz] |
---|---|---|
author | Alice Wang <aliceywang@google.com> | Thu May 16 15:41:34 2024 +0000 |
committer | Alice Wang <aliceywang@google.com> | Fri May 24 09:22:41 2024 +0000 |
tree | 3fd5fbe241dfe342e62ae4a42fdf56f2eb2d2c95 | |
parent | 0ea5497ce463b89a5d9a09d88c8e8e435029c987 [diff] |
Allow AVF remote attestation to be disabled This CL adds a variable in makefile that allows the AVF remote attestation feature to be disabled easily. The remote attestation feature is opt-in by default, as it is a strongly recommended feature from Android V. It will be disabled if PRODUCT_AVF_REMOTE_ATTESTATION_DISABLED is set to true in the Makefile, otherwise it will be enabled when the feature flag RELEASE_AVF_ENABLE_REMOTE_ATTESTATION is on. Bug: 331269709 Bug: 341292601 Test: run VM remote attestation on Pixel 6 and check it is disabled Change-Id: Id48ebd0eacf0d7a6c69b9100aee5ab6e4f112fe5
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.