-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Guidance on avoiding STL incompatibilities #62
Comments
One option that seems fairly good given the discussion in #69, might be to allow setting of the shared library name on the Java side and then allow users to statically link fbjni into their native code. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thanks for a great library :)
This is at least mostly a question: I know there's trickiness in avoiding STL conflicts on Android and that the prebuilt versions of fbjni use (an unknown version of) the c++_shared STL. Do you have any guidance on avoiding issues conflicting STL issues with fbjni? Should we always be building from source, rather than using the prebuilt aar?
The text was updated successfully, but these errors were encountered: