Gitiles
Code Review Sign In
gerrit.omnirom.org / android_build / b52bd8f89ef3120125fafd7cf9e1214d760e2f13
commitb52bd8f89ef3120125fafd7cf9e1214d760e2f13[log] [tgz]
authorLiana Kazanova <lkazanova@google.com>Tue Dec 03 21:47:31 2024 +0000
committerGerrit Code Review <noreply-gerritcodereview@google.com>Tue Dec 03 21:47:33 2024 +0000
treec71a85beb7095a82e2f30b344f10373f5b26ea55
parent6b1a0e1d0a06ce325ab8db6b824e52196dedb887 [diff]
Revert "Drop RRO autogeneration for soong apps"

Revert submission 3362490-autogen_app_overlay

Reason for revert: DroidMonitor: Potential culprit for http://b/382076898 - verifying through ABTD before revert submission. This is part of the standard investigation process, and does not mean your CL will be reverted.

Reverted changes: /q/submissionid:3362490-autogen_app_overlay

Change-Id: I297faa401f2663d338ba2297ea70dc85b32a0f5b
1 file changed
tree: c71a85beb7095a82e2f30b344f10373f5b26ea55
  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.