| commit | 0d1d98157a9797ffa9b1af59f3f5c74e480fc007 | [log] [tgz] |
|---|---|---|
| author | Jeongik Cha <jeongik@google.com> | Thu Aug 20 20:21:36 2020 +0900 |
| committer | Jeongik Cha <jeongik@google.com> | Mon Aug 24 23:16:19 2020 +0900 |
| tree | 3243eb626edf69622e5d89512a402797b8d46b2e | |
| parent | ec23cbb7d6359094c7ed5076e205b6f5905e1ddc [diff] |
Introduce BOARD_CURRENT_API_LEVEL_FOR_VENDOR_MODULES If BOARD_CURRENT_API_LEVEL_FOR_VENDOR_MODULES has a numeric value, it replaces "current" or "system_current" with the version which the flag indicates. Bug: 163009188 Test: BOARD_CURRENT_API_LEVEL_FOR_VENDOR_MODULES=29 m, and then check if every vendor java module's sdk_version is 29 if its sdk_version was current. Change-Id: I8c7cf21563b984b8e9ef398192031b1f66d96494
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.