| commit | 6ef5779c988af610e5ff18866479e5a8ff296d9d | [log] [tgz] |
|---|---|---|
| author | Ulya Trafimovich <skvadrik@google.com> | Thu Apr 08 11:47:00 2021 +0100 |
| committer | Ulya Trafimovich <skvadrik@google.com> | Tue Apr 13 12:42:44 2021 +0100 |
| tree | 4fc019c1e63637d4ebbebf5c26999da7a2ce1dbc | |
| parent | d58ae982cf87f8a9db0fae74ebeabe423a12582a [diff] |
Don't expect all Java modules to have a manifest. Some libraries that go through manifest_check do not have a manifest or APK, so there is nothing to check LOCAL_USES_LIBRARIES and LOCAL_OPTIONAL_USES_LIBRARIES against. Handle it as if the manifest had zero <uses-library> tags: don't fail the build unless the module has non-empty LOCAL_USES_LIBRARIES or LOCAL_OPTIONAL_USES_LIBRARIES. Bug: 132357300 Test: lunch cf_x86_64_phone-userdebug && m Change-Id: I4b1317cfbd93cb6129caba51b56081307a564442
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.