Hi,
Background:
In Sony Mobile, we started consider to package our OEM specific UI
elements/resources into an apk whose extensions are then shared among our
original applications. For this purpose, we have explored the dynamic
resource linking capability provided by AAPT which was first introduced in
Android Lollipop MR1. Below is an example which adopted the link method
configured in our platform build.
/SharedLibrary <-- dynamically linked resource (.apk)
(Android.mk)
LOCAL_AAPT_FLAGS := --shared-lib
LOCAL_PACKAGE_NAME := SharedLibrary
/SonyGeneric <-- .apk to use /SharedLibrary
(Android.mk)
LOCAL_RES_LIBRARIES := SharedLibrary
(AndroidManifest.xml)
<uses-library android:name="com.google.android.test.shared_library" />
LOCAL_RES_LIBRARIES := SharedLibrary
"SharedLibrary.apk" is eventually installed under /system/app and the
dynamic link can be successfully resolved by SonyGeneric.apk
Need help with:
How is this situation configured if both the dependent linked resource and
the original application are built using Gradle/Android Plugin for Gradle?
Is it even possible to run "aapt --shared-lib" in the application build
tool?
Below are what we have tried and so far no success.
/SharedLibrary <-- dynamically linked resource (.aar)
(build.gradle)
android {
aaptOptions {
additionalParameters = ['--shared-lib']
}
}
/SonyGeneric <-- .apk to use /SharedLibrary
(build.gradle)
android {
aaptOptions {
additionalParameters ['-I',
'SharedLibrary/build/ouputs/aar/SharedLibrary-release.aar'
}
}
Looking forward to your great advice.
BR, Huaxing Sun, Sony Mobile in Tokyo, Japan
--
You received this message because you are subscribed to the Google Groups
"adt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to adt-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
