| commit | d058de4a773ac610a00941aa21342c892fcc6dc8 | [log] [tgz] |
|---|---|---|
| author | Nan Zhang <nanzhang@google.com> | Fri Apr 27 16:15:35 2018 -0700 |
| committer | Nan Zhang <nanzhang@google.com> | Wed Jun 06 13:32:54 2018 -0700 |
| tree | ff53be2f753ae8374e5e4038a47b59e31da9a4a5 | |
| parent | b2a5515585edfb0b0adbf60f99e06c0ad2dd1d75 [diff] |
Change droiddoc.mk to support metalava
Test: Manually checked-in prebuilt metalava.jar to my local src tree and
compare the results between old and new docs/stubs generation.
Bug: b/78245848
Change-Id: Ied81cba53c483d4cfb5720e6325b299a1b32104e
Merged-In: I44b4b8ba248ad4deafbb6462e6f7398f15bd2845
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.