You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
my application includes other native binaries that depend on libc++, it would be nice if you distributed objectbox binaries without libc++ statically linked so as to reduce the binary size and ram usage.
Thanks for the suggestion. However the docs you link specifically warn against using the shared runtime for JNI libraries distributed through an AAR, like ObjectBox for Android does.
Caution: JNI libraries distributed with Java AARs must not use the shared runtime to avoid conflicting with other libraries and the app.
yes, I am aware of the drawbacks of having multiple libraries sharing the same libc++ shared library, especially if the final developers are not careful to build all libraries with the same version of ndk and libc++.
Personally, I manually rebuild each library with native code for my app and it's a pity to have done all this work on so many libraries and stay with static libc++ only for objectbox.
tldr:
So I don't think this is possible?
is possible but only not recommended if you do not know what you are doing.
my application includes other native binaries that depend on libc++, it would be nice if you distributed objectbox binaries without libc++ statically linked so as to reduce the binary size and ram usage.
Describe the solution you'd like
android ndk allows you to switch between static and dynamic libc++ in a simple way
https://developer.android.com/ndk/guides/cpp-support
The text was updated successfully, but these errors were encountered: