784db1a741
We are bringing up support for ARM Memory Tagging Extension in the platform, but the required patches have not yet landed in the upstream kernel. This change adds support for a product variable that products may set to true to declare support for an experimental userspace interface to MTE. Setting the variable to true causes a product configuration to be enabled which will activate code in bionic and scudo that uses the interface. This variable should not be set to true in shipping products because the userspace interface has not been finalized and is subject to change. Once the support patches have landed in the kernel, bionic and scudo will be changed to use the official interface and the variable will be removed. Bug: 135772972 Change-Id: Ie3d2619bc09c134e0da073c65805e7ec049687e1 |
||
---|---|---|
common | ||
core | ||
packaging | ||
target | ||
tests | ||
tools | ||
.gitignore | ||
buildspec.mk.default | ||
Changes.md | ||
CleanSpec.mk | ||
Deprecation.md | ||
envsetup.sh | ||
help.sh | ||
navbar.md | ||
OWNERS | ||
README.md | ||
tapasHelp.sh | ||
Usage.txt |
Android Make Build System
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.