commit | 4a602955d09c65fd0f8dece48c30e7c2551e9609 | [log] [tgz] |
---|---|---|
author | Jiyong Park <jiyong@google.com> | Tue Oct 16 10:59:55 2018 +0900 |
committer | Jiyong Park <jiyong@google.com> | Wed Oct 17 10:21:33 2018 +0900 |
tree | 56bcc248a55bc0d7583f8ea49cb5a31a8af4a630 | |
parent | 4e90c3f9a5243160ee893f3b2aa211a5e995cef9 [diff] |
android.test.{base|mock} are added as optional libraries. The two java shared libraries do not exist in the pre-P devices. Therefore, marking the dependencies to the libraries as optional so that an app is still installable to the old devices. This is safe because the classes in the java shared libs exist in other shared libraries (bootclasspath or android.test.runner). Bug: 113800422 Test: run aapt dump badging on the built GtsBackupHostTestCases uses-library tags for android.test.base|mock are with android:required=false, while the same tag for other libs are without the attribute. Change-Id: Ieb7c1429077aaf6899e214a217d9455d95dbfea6
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.