Gitiles
Code Review Sign In
gerrit.omnirom.org / android_build / 000e31c9ed8b8753b922db7416f6496254747920
commit000e31c9ed8b8753b922db7416f6496254747920[log] [tgz]
authorJustin Yun <justinyun@google.com>Wed Feb 28 20:54:14 2024 +0900
committerJustin Yun <justinyun@google.com>Wed Feb 28 21:01:40 2024 +0900
treeee497b6ad953704526c2a6d04f756fc8655748ff
parent1ffcbde28e92ad4ae4c094d0dc9af025ff75b469 [diff]
Define PRODUCT_SHIPPING_VENDOR_API_LEVEL

Devices may set its first vendor api level to
PRODUCT_SHIPPING_VENDOR_API_LEVEL. This will manually set to
ro.vendor.api_level and will be used by tests.

If this value is not defined, init process will automatically
calculate the ro.vendor.api_level property for tests.

Bug: 326164316
Test: Check vendor/build.prop
Change-Id: I89f844ffaad9e3e39deab1c680bd1f7f17f4d8ad
2 files changed
tree: ee497b6ad953704526c2a6d04f756fc8655748ff
  1. ci/
  2. common/
  3. core/
  4. packaging/
  5. target/
  6. teams/
  7. tests/
  8. tools/
  9. .gitignore
  10. banchanHelp.sh
  11. buildspec.mk.default
  12. Changes.md
  13. CleanSpec.mk
  14. cogsetup.sh
  15. Deprecation.md
  16. envsetup.sh
  17. help.sh
  18. METADATA
  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.