Gitiles
Code Review Sign In
gerrit.omnirom.org / android_build / f274f7cd26901b89d2b141c0df89e4a443e761ba
commitf274f7cd26901b89d2b141c0df89e4a443e761ba[log] [tgz]
authorNick Kralevich <nnk@google.com>Mon Mar 03 16:21:47 2025 -0800
committerGerrit Code Review <noreply-gerritcodereview@google.com>Mon Mar 03 16:21:48 2025 -0800
treeb6c3b2cf272035e7690263e2324c094bf2fc10c0
parentf2c78addd495210722e8138c67444dd5419e9b7b [diff]
Revert "Use -target-feature for MTE"

Revert submission 3493411-target_feature_mte

Reason for revert: The infrastructure upgrades necessary to support
this change still have not been completed. To submit this change,
re-client needs to be upgraded to v0.170 or greater.

Reverted changes: /q/submissionid:3493411-target_feature_mte
Bug: 366222162
Bug: 399925046

Change-Id: Id9ddce2546f6db1386d98fac44046f21878268d0
1 file changed
tree: b6c3b2cf272035e7690263e2324c094bf2fc10c0
  1. backported_fixes/
  2. ci/
  3. common/
  4. core/
  5. packaging/
  6. target/
  7. teams/
  8. tests/
  9. tools/
  10. .gitignore
  11. Android.bp
  12. banchanHelp.sh
  13. buildspec.mk.default
  14. Changes.md
  15. CleanSpec.mk
  16. Deprecation.md
  17. envsetup.sh
  18. help.sh
  19. navbar.md
  20. OWNERS
  21. PREUPLOAD.cfg
  22. rbesetup.sh
  23. README.md
  24. shell_utils.sh
  25. tapasHelp.sh
  26. 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.