| commit | c4d57494b58c9eb78ddecd63a5a3e9c1618b1ea8 | [log] [tgz] |
|---|---|---|
| author | Mathew Inwood <mathewi@google.com> | Wed Aug 08 14:20:19 2018 +0100 |
| committer | Mathew Inwood <mathewi@google.com> | Mon Aug 13 16:21:21 2018 +0100 |
| tree | 6eed320560e7758fa8edb7dcf17476b0834e8b62 | |
| parent | e318a785495e1557f042c62a5878a496174c6520 [diff] |
Pass public API list to class2greylist tool. This is necessary to allow it to exclude synthetic bridge methods from the generated greylist. We need to be able to apply the @UnsupportedAppUsage annotation to regular (non-bridged) methods, but due to the SDK visibility rules, the synthetic bridge is part of the SDK. Don't do this on build that don't include frameworks/base since the target is not needed and breaks certain builds. Bug: 110868826 Test: m Change-Id: I08f06f38d84945f5473618513c641762bc541e24
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.