commit | b8f16824ad3eb24276bc8bc19334406e9cb978ca | [log] [tgz] |
---|---|---|
author | Jiyong Park <jiyong@google.com> | Mon Apr 23 10:39:54 2018 +0900 |
committer | Jiyong Park <jiyong@google.com> | Mon Apr 23 16:23:57 2018 +0900 |
tree | 2a7560cc429cdc2020c5b555ba4b996f3695ae31 | |
parent | 6181ffa9e712687d6def24e1693e3eb4481f71b0 [diff] |
Set BOARD_SYSTEMSDK_VERSIONS automatically for P-launching device Like BOARD_VNDK_VERSION is automatically set, BOARD_SYSTEMSDK_VERSIONS is also automatically set to the latest supported SystemSDK version when it is unset. Specifically, it is set when 1) it isn't explicitly set by the vendor and 2) the device is P-launching device (PRODUCT_SHIPPING_API_LEVEL >= 28) Bug: 78431725 Test: m -j Test: `get_build_var BOARD_SYSTEMSDK_VERSIONS` return P for 2018 Pixels. Change-Id: I036a07da3ce58bdf22d252b6ef18263c7da3602a
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.