Create an SDK (single jar file) with "so" files

I have to create an SDK that will be easy to use, so I need it to be in a single jar file. Resources are problematic, but what about including ".so" files, which are libraries created by the NDK (usually placed in the "libs / armeabi" folder)?

Is it possible to add ".so" files to a jar file so that anyone using the jar SDK file should not add them to their libs folder in their project?

If so, how, and if not, is there a workaround?

To clarify: who uses the SDK, should use only one jar file, which will contain everything that is needed to use the SDK, including the ".so" files.

Please note that if I put the libs folder (and ".so" in it) into a project that uses the SDK, it works fine. The same thing happens if I use the SDK project as an Android project.

+5
source share
1 answer

In fact, that is what Android, as ADT 17it is. In fact, when you create library projectand import it into another project, it Androidcreates jar file. This is true for native library. Simple, when you create a project library, the folder armeabiwill also be included in jar.

+3
source

All Articles