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
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:
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.
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: