Gitiles
Code Review Sign In
gerrit.omnirom.org / android_build / c09381545ebaff7198ff86368bfe6bf470071751
commitc09381545ebaff7198ff86368bfe6bf470071751[log] [tgz]
authorSpandan Das <spandandas@google.com>Fri Dec 06 20:43:54 2024 +0000
committerSpandan Das <spandandas@google.com>Fri Dec 06 20:56:44 2024 +0000
tree67e8c08090ecdcb4731f4894eade4ce95cd9251f
parent31356199e611f89ef15277220ba8830235eea657 [diff]
Export TARGET_USES_VULKAN as string

Make build.prop has three values for ro.hwui.use_vulkan
- true
- false
- (empty string)

In preparation for validating soong built vendor filesystem, export
TARGET_USES_VULKAN as a string. This allows `gen_build_prop.py` to
create empty `ro.hwui.use_vulkan` (currently it will populate it as
false)

Bug: 382295862
Test: compared vendor build.prop for aosp_cf_x86_64_phone
Change-Id: Ib6a37a950a33e7b06c260bb651347b4fb4e36834
1 file changed
tree: 67e8c08090ecdcb4731f4894eade4ce95cd9251f
  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.