| commit | b67402ecceea2d239340bfef68aaefc3fec7feff | [log] [tgz] |
|---|---|---|
| author | David Brazdil <dbrazdil@google.com> | Wed Aug 22 17:38:02 2018 +0100 |
| committer | David Brazdil <dbrazdil@google.com> | Thu Aug 23 10:38:03 2018 +0100 |
| tree | 3a2af45dd2c2b8574cd830d46d82106eb9d96f65 | |
| parent | ebe17177fee2fdcf7387d51b95eec56cc99dff38 [diff] |
Support hidden API whitelist generated by class2greylist Libcore has support for annotating a virtual method which is known to change its return type in a future release. This annotation is recognized by the dexer and a future-proof bridge method is created. This patch integrates changes in class2greylist to support this annotation into the build system and generation of hidden API lists. Calling class2greylist on each boot classpath module now produces two text files instead of one: signatures for greylisting and now also whitelisting. They are passed on to the hidden API list generating rules in frameworks/base. Bug: 112186571 Test: m appcompat, diff public-list.txt whitelist.txt Change-Id: I9861203e6e07a17d50850892ec13880971457d11
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.