Gitiles
Code Review Sign In
gerrit.witaqua.org / build / 058307923e570d900d27a9f1f5164441b4fc8b93
commit058307923e570d900d27a9f1f5164441b4fc8b93[log] [tgz]
authorJihoon Kang <jihoonkang@google.com>Tue Sep 09 08:36:56 2025 +0000
committerJihoon Kang <jihoonkang@google.com>Tue Sep 09 11:00:36 2025 -0700
treeff026c4f22728f6a8dd8e1bd953c5df1bb4a8f8c
parent66c17e77bb6d2fb0b43eb99fe479e8e52f6a5310 [diff]
fix: Fix Soong-only diffs for aosp_cf_arm64_phone_vendor

Applied automated fixes generated by the Gemini tool.

This change exports the product variable `BOARD_16K_OTA_MOVE_VENDOR` to Soong.

Test: build/soong/scripts/soong_only_diff_test.py aosp_cf_arm64_phone_vendor
Bug: 427983604
Change-Id: Ic4d710ef2ef7c8b49405e9890c7bb430d8d3b50a
1 file changed
tree: ff026c4f22728f6a8dd8e1bd953c5df1bb4a8f8c
  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.