when it is a `java_library` rather than a +`java_sdk_library`, or when the library name is different from its module name, +or when the module is defined in Android.mk rather than Android.bp). But +sometimes a library also needs additional information in its +Android.bp/Android.mk file (e.g. + +To specify a list of libraries for a given modules, use: + +* Android.bp properties: `uses_libs`, `optional_uses_libs` +* Android.mk variables: `LOCAL_USES_LIBRARIES`, `LOCAL_OPTIONAL_USES_LIBRARIES` + +If a library is in `libs`, it usually should *not* be added to the above +properties, and Soong should be able to infer the `` tag. In simple cases Soong is able to infer it from its knowledge of Java SDK +libraries and the `libs` property in Android.bp, but in more complex cases it is +necessary to add the missing information in Android.bp/Android.mk manually. Since the build system does not have +access to the manifest contents, that information must be present in the build +files.
![recompress jar file mod recompress jar file mod](https://i.stack.imgur.com/mk21w.png)
+++ -1,5 +1,49 Build System Changes for Android.mk Writers +# Dexpreopt starts enforcing `` checks (for Java modules) + +In order to construct correct class loader context for dexpreopt, build system +needs to know about the shared library dependencies of Java modules listed in +the `` tags in the manifest. Merge "Revert "Add new llndk library, libneuralnetworks_shim.so"" diff -git a/Changes.md b/Changes.md