commit | c0f738c974ea94f59d83c90afaa0cfccfe71440a | [log] [tgz] |
---|---|---|
author | Jiyong Park <jiyong@google.com> | Thu Jun 21 14:18:54 2018 +0900 |
committer | Jiyong Park <jiyong@google.com> | Thu Jun 21 14:18:54 2018 +0900 |
tree | abd08402f21df362727ad1dbdc9c1144fa39a836 | |
parent | 6291a4a258239fc91d43b392f35358b0379f4675 [diff] |
check-vndk-list is run even when VNDK is not enabled check-vndk-list has not been run when VNDK is not enabled (i.e. BOARD_VNDK_VERSION is unset). This was problematic because there is a chance that a CL which passed pre-submit tests can fail the post-submit tests when the targets selected for the pre-submit tests are all without VNDK enforcement. In order to prevent the case, check-vndk-list is executed regardless of whether BOARD_VNDK_VERSION is set or not. Bug: 110424280 Test: m -j on sailfish Test: m -j on sailfish fails after adding an arbitrary library to VNDK Change-Id: Ia7427be2a297940a9e9c9f46cb058245596171c9
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.