commit | 82f0a2d751f7349b2b7e08f68ae5291f618d2ea7 | [log] [tgz] |
---|---|---|
author | Yike <yikezh@google.com> | Wed Aug 31 17:46:13 2022 +0800 |
committer | Yike Zhang <yikezh@google.com> | Thu Sep 08 07:59:20 2022 +0000 |
tree | 5849ce94eacde255def5fe26b438a0aeba11a1d5 | |
parent | 0ab4e219396f10ce4e56a0afd1fe479ed92b0a61 [diff] |
Export Java libraries into module-info Some Java modules are defined in Android.mk and they declare dependencies in eigther LOCAL_STATIC_JAVA_LIBRARIES or LOCAL_JAVA_LIBRARIES. This information needs to present in module_info.json and be exported to properly generate Bazel targets that include these dependencies. Test: m out/target/product/coral/module-info.json Bug: 245686435 Change-Id: I77bc8de59f1d46bb098463066e1f52b98ebae955
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.