Remove unnecessary Proguard builds

Previously, the proguard_dict was calculated based on build targets.
Later, it was modified to generate for all installed modules, causing
unnecessary Proguard builds for modules that are not included in the
final image, which increased overall build time.

To optimize, this change checks installed files of each module and
removes modules from Proguard list if none of their files are in image.
This reduces build time by skipping Proguard processing for modules
like Settings and SystemUI not included in vendor-only builds such as
aosp_cf_x86_64_phone_vendor.

Test: lunch sdk_phone64_x86_64-trunk_staging-userdebug & m
validated by verifying Proguard results remain identical before and
after applying the patch.

Change-Id: I52f4c548accf2a45ea4355553def3bca187d2f9a
1 file changed
tree: 073c047f9db15e9715aa7d4d9f956fa9e59c3135
  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.