Refactor how jni_libs dependencies are added
This CL brings three changes in how jni_libs are depended on. 1. SDK variants of the jni_libs are depended on only when they can be embedded. This is because SDK variants are not installable. Previously, app could depend on SDK variants without embedding them, but this didn't cause a problem because the installation of the jni libs was done in Make. However, as it's done in Soong, we need to depend on a correct variant. 2. Non-SDK variants of the jni_libs are now tagged with jniInstallTag. This automatically installs the libraries along with the app. The installation of the jni libs is no longer done in app. 3. checking of the sdk version of the jni libs is done only when they are embedded. Doing the check even when the libs are not embedded triggers a lot of false alarms. Note that with #1, many platform apps have started depending on non-SDK variants. Bug: 330276359 Test: m Change-Id: I1bc9ceb8f79b102caeb23476c3fb03989e184a91
Loading
Please register or sign in to comment