| commit | 924d2d929d938cfc79b787cc1e217c714becbe0b | [log] [tgz] |
|---|---|---|
| author | Hung-ying Tyan <tyanh@google.com> | Wed Sep 19 16:52:58 2018 +0800 |
| committer | Hung-ying Tyan <tyanh@google.com> | Wed Sep 19 18:00:19 2018 +0800 |
| tree | 052652ffbd7227f45a5603e15dd6f759be79288f | |
| parent | 5f8eb7c553bbee5cc5ceea30bf189164f5244146 [diff] |
Condition VNDK check on TARGET_BUILD_APPS
Bug: 113560265
Test: (with the topic)
Test: mv prebuilts/vndk/v28 v28
Test: make TARGET_PRODUCT=aosp_arm TARGET_BUILD_APPS=Launcher3 TARGET_BUILD_VARIANT=userdebug
--> build pass
Test: lunch aosp_arm-userdebug
--> error: VNDK version 28 not found
Test: mv v28 prebuilts/vndk/v28
Test: lunch aosp_arm-userdebug
--> no error
Change-Id: Ifb553a5ee4cec8b3f3b79aebdf824d64571fa817
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.