| commit | af482ea053f542944de3d6b4256af917fbf6e5f5 | [log] [tgz] |
|---|---|---|
| author | Tobias Thierer <tobiast@google.com> | Fri Jan 10 15:56:46 2020 +0000 |
| committer | Tobias Thierer <tobiast@google.com> | Sat Jan 11 16:07:13 2020 +0000 |
| tree | f71a5183861e32c38af68aefa47a1eb6701e9085 | |
| parent | c30b734f427915ecc92677017b71d6e005d806bf [diff] |
Disallow unnamed package on the bootclasspath. There are currently no classes on the bootclasspath that live in the unnamed package (empty package name). This CL explicitly forbids it. This has the side effect of guarding against some classes of bugs, for example R8 has functionality to generate some helper classes in the unnamed package that should not be on the to bootclasspath because they would hide corresponding classes in Applications. Strictly speaking I believe that the "not package_name or " part of the condition in the touched script is not needed because LoadWhitelist() already skips empty lines and doesn't add "^$" to the whitelist regex, but relying on this seems very fragile. If there ever is a need to have classes in the bootclasspath's unnamed package in future then we can always change this again. Bug: 147480264 Test: Treehugger Change-Id: Ic310dd0779dde133b3a5c3039ea5b70d31331a9b
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.