Cfrgtkky

I have a Gradle project that publishes an Android library to my maven server (I will refer this as project A). The library is packaged as an .aar, but only contains native .so files. The structure looks like this:

libraryA.aar

 |  

 +-- jni

 |  |  

 |  +-- arm64-v8a

 |  |   |  

 |  |   +-- native_lib_A.so

 |  |

 |  +-- armeabi-v7a

 |  |   |  

 |  |   +-- native_lib_A.so



 ...etc

Now I have another Android project that builds a different native C/C++ library (I will refer this as project B). B depends on the library A.

From project B's build.gradle, I can easily pull library A from my maven server like this:

dependencies {

    implementation 'com.example:libraryA:1.0.0'

}

However, I can't find any simple clean way to link the .so files from the prebuilt library A with the library B.

The best that I can do is write a messy Gradle task to unzip the aar and copy the .so files to another location that library B's make file (or CmakeList) can use. I also had to write a messy Gradle task in project A to stuff the header files into the aar in some non-standard location so that project B could use them.

So, I would like to know if there is a better way to resolve Android native dependencies when one native library depends on another pre-built native library that is packaged as an .aar and published on a Maven server?