commit | b8fb0de02faf8f29a1c1b1f61454c743c9a6603c | [log] [tgz] |
---|---|---|
author | Ralph Nathan <ralphnathan@google.com> | Mon Aug 13 14:35:03 2018 -0700 |
committer | David Brazdil <dbrazdil@google.com> | Wed Aug 15 17:51:55 2018 +0100 |
tree | a6c754a9580ef5e5534ea450187a2dfae0135688 | |
parent | 5d1b46784d9444b48b27981b4824c2676ff60ea1 [diff] |
Allow products to define their own hidden api stubs This enables other verticals/products to expand the list of APIs that apps can call on those devices. Bug: 112190341 Test: local test with app Merged-In: I4dc983273a1beb83d0b81ab026945880a10bbd8c Change-Id: I4dc983273a1beb83d0b81ab026945880a10bbd8c (cherry picked from commit f9bf755d0a7d4e77061995b045ad5ef42b3ebd78)
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.