Gitiles
Code Review Sign In
gerrit.omnirom.org / android_build / 737f6e5c1845c9cf06eb8b3b0f82e8c10e9fcda5
commit737f6e5c1845c9cf06eb8b3b0f82e8c10e9fcda5[log] [tgz]
authorJooyung Han <jooyung@google.com>Thu Oct 12 10:03:50 2023 +0900
committerJooyung Han <jooyung@google.com>Thu Oct 12 10:39:58 2023 +0900
tree3ec63456c539bfd3bed448ef585bb838b31c61a7
parent057a3dd4293236f7eecf2876fb90e46b7fe2cb4c [diff]
APEX extraction rule mentions APEXes

so that it's triggered even when APEX list shrinks.
(-d explain will print "command line changed for ...")

To repro:
- Pick one VAPEX with vintf fragment.
- Copy the fragment to /vendor/etc/vintf/manifest (DEVICE_MANIFEST_FILE)
- `m check-vintf-all` should fail
- Remove the APEX from PRODUCT_PACKAGES
- `m check-vintf-all` should pass

Bug: 304769672
Test: m check-vintf-all
   (see above)
Change-Id: Iae9da91105faebfb8a5127fbb02a414b9ffdca10
1 file changed
tree: 3ec63456c539bfd3bed448ef585bb838b31c61a7
  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. cogsetup.sh
  13. Deprecation.md
  14. envsetup.sh
  15. help.sh
  16. METADATA
  17. navbar.md
  18. OWNERS
  19. PREUPLOAD.cfg
  20. rbesetup.sh
  21. README.md
  22. shell_utils.sh
  23. tapasHelp.sh
  24. 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.