Gitiles
Code Review Sign In
gerrit.omnirom.org / android_build / 71bff6a6a19a91138a47b6ef3f6848248e55012b
commit71bff6a6a19a91138a47b6ef3f6848248e55012b[log] [tgz]
authorJared Duke <jdduke@google.com>Fri Dec 27 23:20:03 2024 +0000
committerJared Duke <jdduke@google.com>Fri Dec 27 23:20:03 2024 +0000
tree96eefeac51c53b51e2446db31b2a50972122ccb2
parentb5cb266fd6a8fc7f59940903b9c41884d4a55f0e [diff]
Tweak WeaklyReferencedCallback keep rules

Adjust the semantics so that we only prevent optimization, and we avoid
unnecessary keeps for synthetically generated members.

This should have no effective impact on weakly referenced lifecycle
semantics, though the generated dex code might be slightly different.

Bug: 349245577
Test: FULL_SYSTEM_OPTIMIZE_JAVA=true m services
Flag: EXEMPT refactor
Change-Id: I7a6de2d8db593a5336f94448f18a75482e4ed349
1 file changed
tree: 96eefeac51c53b51e2446db31b2a50972122ccb2
  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.