alexeymin added a comment.
http://doc.qt.io/qt-5/deployment-android.html at the bottom of the page there is an example of usage scenario for `qmake` project: > ANDROID_EXTRA_LIBS: A list of external libraries that will be copied into your application's library folder and loaded on start-up. This can be used, for instance, to enable OpenSSL in your application. Simply set the paths to the required libssl.so and libcrypto.so libraries here and OpenSSL should be enabled automatically. In Qt Creator you can manually specify extra libs in project build settings: F5878332: qt creator project android settings extra libs.png <https://phabricator.kde.org/F5878332> After that, the following is added to *.pro file for qmake: contains(ANDROID_TARGET_ARCH,armeabi-v7a) { ANDROID_EXTRA_LIBS = \ $$PWD/android/arm-linux-androideabi-4.9/libcrypto.so \ $$PWD/android/arm-linux-androideabi-4.9/libssl.so } With this variable qmake generates a proper JSON file for `androiddeplyoqt`, containing `"android-extra-libs"` with full path to specified libs, and so they are included in result APK. Step above work for qmake project. For cmake, using ECM Android toolchain file you have no way to specify dependencies manually, without this patch. REPOSITORY R240 Extra CMake Modules REVISION DETAIL https://phabricator.kde.org/D13198 To: alexeymin, apol Cc: kde-buildsystem, kde-frameworks-devel, michaelh, ngraham, bruns
