Further refine VisibleForTesting rules

Additional analysis revealed more edge cases where external library
code was getting kept unnecessarily. Further refine the keep rules to
avoid these cases. Now, we only apply keep globally for the
`com.android.internal.annotations.VisibleForTesting` annotation.

VisibleForTesting annotations defined externally (e.g., by androidx or
guava) will *only* be respected in platform-defined packages. This
helps trim unused code from deps like gRPC and Dagger, saving up to
~hundreds of KB per package that uses these libraries.

Bug: 248580093
Test: m + verify exclusion of external test code (e.g., from dagger)
Change-Id: Iab7559c08d3ae1ac74f18e3cf3a1b4828a3736cf
1 file changed
tree: 993c0bfc8ac5cb7fc2c6b51570590639fd50fbbb
  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. finalize-aidl-vndk-sdk-resources.sh
  15. finalize-cleanup.sh
  16. finalize-locally-mainline-sdk.sh
  17. finalize-sdk-rel.sh
  18. finalize-step-1-for-build-target.sh
  19. finalize-step-1.sh
  20. finalize-step-2-for-build-target.sh
  21. finalize-step-2.sh
  22. finalize_branch_for_release.sh
  23. help.sh
  25. navbar.md
  26. OWNERS
  27. PREUPLOAD.cfg
  28. rbesetup.sh
  29. README.md
  30. shell_utils.sh
  31. tapasHelp.sh
  32. 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.