Gitiles
Code Review Sign In
gerrit.omnirom.org / android_build / 80b53b8c77990a9ead79eb1eb54fa34610bdc946
commit80b53b8c77990a9ead79eb1eb54fa34610bdc946[log] [tgz]
authorEvgenii Stepanov <eugenis@google.com>Thu Jun 08 15:40:39 2023 -0700
committerEvgenii Stepanov <eugenis@google.com>Tue Jun 13 13:11:52 2023 -0700
tree66d39ae70d707602d8a7ebc8d53160a7ec049d6e
parent9448754144e407576462df6faa1dfe9e9346506f [diff]
Move MTE mode settings to a product variable.

Allow product configuration of memtag target list by
moving the current set into a product variable instead of the various
.bp files.

The default list of memtag targets can be found in
  build/make/target/product/memtag-common.mk

This is NFC as all targets in the list already have "memtag_heap: true"
in the build files.

Bug: 280343521
Test: no functional change
Change-Id: I5954fde05256e00a8e01c114ad522f50ed0cfa9f
6 files changed
tree: 66d39ae70d707602d8a7ebc8d53160a7ec049d6e
  1. common/
  2. core/
  3. packaging/
  4. target/
  5. tests/
  6. tools/
  7. .gitignore
  8. banchanHelp.sh
  9. buildspec.mk.default
  10. Changes.md
  11. CleanSpec.mk
  12. Deprecation.md
  13. envsetup.sh
  14. help.sh
  15. METADATA
  16. navbar.md
  17. OWNERS
  18. PREUPLOAD.cfg
  19. rbesetup.sh
  20. README.md
  21. shell_utils.sh
  22. tapasHelp.sh
  23. Usage.txt
README.md

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.