Emit PRODUCT_COMPRESSED_APEX as build prop

The value will be set as sysprop: apexd.config.compressed_apex. This
property tells apexd/init that there's no compressed apexes.

For go/mount-apex-before-data feature to work, there should be no
compressed apexes. If not, init/apexd should run with the feature
disabled.

PRODUCT_COMPRESSED_APEX is to control whether to install compressed
APEXes or not. (If it's `false`, there'll be no compressed apexes.)
Emitting this as sysprop helps init/apexd to know the fact.

Otherwise, apexd/init need to scan the builtin apex directories (e.g.
/system/apex) to see if there's no compressed apexes or not, which would
make the boot slower because it involves lots opening directories and
APEX files.

Bug: 381173074
Test: lunch aosp_cf_x86_64_phone-trunk_staging-userdebug
Test: m && cvd create && adb shell getprop apexd.config.compressed_apex
Change-Id: Ia3c172be5f0906b6fbaebaf450ee24b22bf358cb
1 file changed
tree: d98591e5c7b80a0bb8005729e6440b76215bc150
  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.