Gitiles
Code Review Sign In
gerrit.omnirom.org / android_build / f4c9330e24ff8dd1935531ad2238e65d7e8b4163
commitf4c9330e24ff8dd1935531ad2238e65d7e8b4163[log] [tgz]
authorKiyoung Kim <kiyoungkim@google.com>Mon Jan 29 13:12:24 2024 +0900
committerKiyoung Kim <kiyoungkim@google.com>Tue Jan 30 17:10:39 2024 +0900
tree8ed4da5d01d5a4fc479d6189e42eb97dbaff243f
parentf39e4a22730acb9a9b19283b41481de8b115ca43 [diff]
Rename LOCAL_USE_VNDK

LOCAL_USE_VNDK property refers if the module uses VNDK, and this
property is being used to check if the module is installed in vendor or
product. However, the term no longer makes sense with VNDK deprecation,
so it should be renamed. Similar to change in aosp/2897612, rename
LOCAL_USE_VNDK as LOCAL_IN_VENDOR or LOCAL_IN_PRODUCT.

Bug: 316829758
Test: AOSP CF build succeeded
Change-Id: Icfd1707953eba2e29044468ab6728b39d7998048
12 files changed
tree: 8ed4da5d01d5a4fc479d6189e42eb97dbaff243f
  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.