| commit | cd06fe34e0cc9972a0de4db993da309c9f6b1b2e | [log] [tgz] |
|---|---|---|
| author | Jiyong Park <jiyong@google.com> | Fri Apr 27 16:21:00 2018 +0900 |
| committer | Jiyong Park <jiyong@google.com> | Tue May 01 09:32:11 2018 +0900 |
| tree | 8ba578a7b4a5cef2a34770f029fa95ae3454ed6f | |
| parent | 6023db8844b79ca27a9f780135a4f25242f78a0a [diff] |
sdk lib name can be in LOCAL_[STATIC_]JAVA_LIBRARIES
When an sdk lib name (a module defined with java_sdk_library{...}) is
listed in LOCAL_JAVA_LIBRARIES or LOCAL_STATIC_JAVA_LIBRARIES, the name
is translated to the stubs lib name of the sdk lib.
We have to support this at least until all existing references to sdk
libs are all correctly converted to LOCAL_SDK_LIBRARIES.
Bug: 77575606
Test: m -j
Change-Id: I8cff668afd6b5f265cc7ae6fe6f5fa36b76b8334
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.