Update: it looks like merging the .aar files manually without any need of signing them works just fine :-)
On Fri, May 27, 2016 at 11:18 AM, Iovene, Salvatore <salvatore.iovene at intel.com> wrote: > Hi, > when I build Iotivity for Android, based on the TARGET_ARCH I select, > I get one of the following files: > > ./android/android_api/base/build/outputs/aar/iotivity-base-armeabi-v7a-debug.aar > ./android/android_api/base/build/outputs/aar/iotivity-base-x86-debug.aar > > It seems to me that the only difference between these two archives, is > that one contains the jni/armeabi-v7a directory, and the other > contains the jni/x86 directory, with the appropriate native libraries > inside. > > However, it would be great if I could merge these two .aar files, and > I suppose Android would know how to load the correct native libraries > at runtime. > > Can the build system do this automatically? > > If not, I suppose I could manually merge them and then somehow re-sign > the .aar file? Any tips on how to do this? > > TIA, > Salvatore > > -- > Salvatore Iovene <salvatore.iovene at intel.com> > Linux Software Engineer > Intel Open Source Technology Center, Finland > Tel.: +358504804026 -- Salvatore Iovene <salvatore.iovene at intel.com> Linux Software Engineer Intel Open Source Technology Center, Finland Tel.: +358504804026
