Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct
Android N support
-
Hello,
With Android N, Google are slowly getting rid of OpenSSL in favor of their own flavor (no pun intended): as a result when trying to run on Android N, any code using SSL will get errors regarding libcrypto.so and libssl.so.
Any ideas when we will be able to use Qt on this platform?
-
Hi,
Maybe not a direct answer but if you need OpenSSL support for your application, you can build OpenSSL for Android and ship it with your application.
In any case, you might want to bring that point on the Qt Android development mailing list. You'll find there Qt's Android port developers/maintainers. This forum is more user oriented.
-
Hi,
To help others that might be in the same situation: building OpenSSL for Android, then putting libssl.so and libcrypto.so in <project>/android/libs/armeabi-v7a/ did the trick!
-
Good :)
Then please mark the thread as solved using the "Topic Tools" button so that other forum users may know a solution has been found :)
-
@Geraud I've just built openssl 1.0.2h for Android and it has correctly generated the libssl.so.1.0.0 and libcrypto.so.1.0.0 (using this guide http://stackoverflow.com/questions/11929773/compiling-the-latest-openssl-for-android).
I've read that Android does not support versioned libraries, also if I rename the .so.1.0.0 to .so.
Is this true? How do you build a non-versioned version of the library?
And what about x86..should I put the x86 libraries in android/libs/x86 ?
