commit | e5665cdb4e6f4b3031718a9a8e49d67f68a51702 | [log] [tgz] |
---|---|---|
author | Tobias Thierer <tobiast@google.com> | Tue Mar 27 00:15:50 2018 +0100 |
committer | Tobias Thierer <tobiast@google.com> | Tue Mar 27 00:33:18 2018 +0100 |
tree | 40fb7daa1c10d47aa8cfa09e572352994148ad43 | |
parent | 3cf75cf2bb9f61f27e74af91c1811a92b7aa4982 [diff] |
javadoc/droidoc: Don't add .jar files to sourcepath. javadoc expects directories on the sourcepath, not jar files. The original commit 88b607994a148f4af5bffee163e39ce8296750c6 in 2009 was already passing the jar files, and every revision since then seems to have kept this habit through cargo cult. This CL removes the superfluous jar file arguments from the sourcepath argument to javadoc. Test: Treehugger Bug: 76436487 Change-Id: 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.