| commit | eadd1bdb8e6d343be7cc67d4d2cd3bcb50ebd3dd | [log] [tgz] |
|---|---|---|
| author | Jiyong Park <jiyong@google.com> | Wed Apr 03 22:22:37 2019 +0900 |
| committer | Jiyong Park <jiyong@google.com> | Wed Apr 03 22:35:34 2019 +0900 |
| tree | 1eda0439051fc1194613def80a7b6d89d2f24d2d | |
| parent | 7369b7622f531b6658c8067750475e4dc964c850 [diff] |
Don't feed framework.jar to proguard for vendor apks We used to add framework.jar to proguard via -systemjars option even for the apks building againsd SDK. This was because the app might have references to hidden APIs via static libraries, etc. However, for vendor apks, the use of hidden API is strictly prohibited. So it is fine to not include framework.jar. Furthermore, including framework.jar even causes problems in some cases; if a java library (e.g., android.hidl.base-V1.0-java) is statically linked to both the app and the framework.jar, -systemjars frameworks.jar forcibly removes classes in the library from the app to have references to the non-public classes in framework.jar. This could fail some compliance tests. Fixing the problem by not raising SDK for apks located in vendor or odm partitions. Bug: 128574081 Test: m Change-Id: If2b658fead5b4bb4d8c023a37eb57a37ad9b741d
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.