Gitiles
Code Review Sign In
gerrit.omnirom.org / android_build / ad7cfb56010cb22c3aa0e70cf71c804352553526
commitad7cfb56010cb22c3aa0e70cf71c804352553526[log] [tgz]
authorJooyung Han <jooyung@google.com>Tue Dec 03 17:04:59 2024 +0900
committerJooyung Han <jooyung@google.com>Tue Dec 03 17:09:37 2024 +0900
treeed1e543d2d3807c10211bd8c5bb9750fe1b2a26d
parent3dc4dfbcdf56348cdd38f22cad7b0d7431ac92a6 [diff]
apex_sepolicy_tests only if default payload type is ext4

apex_sepolicy_tests relies on `deapexer list -Z`, which is only
available to ext4 type.

Hence, when building with other type, it logs error messages like:

  erofs is not supported for `list`.

Until deapexer supports the feature, let's run the test for ext4.

Bug: 353896817
Test: PRODUCT_DEFAULT_APEX_PAYLOAD_TYPE=erofs m droid
Change-Id: Iff5f3b77136a303976d1aec992d048240c1adf52
1 file changed
tree: ed1e543d2d3807c10211bd8c5bb9750fe1b2a26d
  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.