Gitiles
Code Review Sign In
gerrit.omnirom.org / android_build / 09aaa26c060e785e65fda9506934b1303019e841
commit09aaa26c060e785e65fda9506934b1303019e841[log] [tgz]
authorKiyoung Kim <kiyoungkim@google.com>Tue Feb 13 13:38:16 2024 +0900
committerKiyoung Kim <kiyoungkim@google.com>Tue Feb 13 13:40:40 2024 +0900
treed12a2a5b654767d6fcef4d60cbc6ec40fa2e4e65
parent7d2c5ff02d4f0b4c28a9fe72dea533fecbc9c182 [diff]
Move setting default BOARD_VNDK_VERSION value

Current BOARD_VNDK_VERSION is being set from config.mk, but this is
before build system loads release config and checks if VNDK is
deprecated or not. Move this to envsetup so it can set up
BOARD_VNDK_VERSION only when VNDK is not deprecated with flag.

Bug: 324976878
Test: mainline release target build succeeded

Change-Id: I490cc431038f5cebc40d03c98d2666eaba906664
2 files changed
tree: d12a2a5b654767d6fcef4d60cbc6ec40fa2e4e65
  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.