Crashlytics Ndk Multi Androidndkout Path Support

I use Fabric Crashlytic to impove my native code performance. I have multi .so library in both app project and jar library project. In my app's build.gradle,here it is: crashlytics

Solution 1:

Matt from Crashlytics here!

UPDATE

As of version 1.23.0, the Fabric plugin supports automatic detection of paths for native binaries when using the Android plugin for Gradle 2.2.0+ with the externalNativeBuild DSL. If using this, you should simply remove the androidNdkOut and androidNdkLibsOut properties from your crashlytics block.

---

Currently we don't have support for defining multiple directories for your native libraries. However, a very simple workaround for this is to define a Gradle task which copies your debug and release .so files from both projects into a common, temporary directory (e.g. temp/ndkout/... and temp/ndklibsout/) and then set your androidNdkOut and androidNdkLibsOut properties to those directories.

One thing to note: you'll need to maintain the architecture-specific folder structure under each set of directories! Here's a full example to give you an idea:

temp/
-- ndkout/-- armeabi-- libappproject.so-- libjarproject.so-- x86-- libappproject.so-- libjarproject.so
  ...
-- ndklibsout/-- armeabi-- libappproject.so-- libjarproject.so-- x86-- libappproject.so-- libjarproject.so
  ...