QML Image: TLS initialization failed

[qcoderpro]

@sierdzio

It says: By default, an SSL-enabled Qt library dynamically loads any installed OpenSSL library at run-time

I'm on Windows.

[sierdzio]

Yes, well there isn't any installed OpenSSL library on Windows :D

[qcoderpro]

@sierdzio

But I've installed OpenSSL using Qt!
You mean I can't load an image from the Internet on Windows!?

This guy is running that project on Windows successfully!

[sierdzio]

@qcoderpro said in QML Image: TLS initialization failed:

@sierdzio

But I've installed OpenSSL using Qt!

But it's not a system-wide installation.

You mean I can't load an image from the Internet on Windows!?

You can. Just link OpenSSL to your project, or place OpenSSL DLLs close to the .exe.

[qcoderpro]

@sierdzio

Just link OpenSSL to your project

How to do that on Windows?

[sierdzio]

• find where your OpenSSL installation is
• in your .pro file (I assume you're using qmake), add:

LIBS+=path/to/openssl/libs
INCLUDEPATH+=path/to/openssl/include

[qcoderpro]

@sierdzio

I've installed both x64 and x86 versions of openssl but the kit I'm using to run the project is x64 so I add: C:\Qt\Tools\OpenSSL\Win_x64\lib

But I'm using CMake. Can I add these two lines just like the .pro file of qmake in it?

LIBS += C:\Qt\Tools\OpenSSL\Win_x64\lib   // (There's no 'libs' folder in the openssl directory)
INCLUDEPATH += C:\Qt\Tools\OpenSSL\Win_x64\include

[sierdzio]

For cmake, you should use FindOpenSSL: https://cmake.org/cmake/help/latest/module/FindOpenSSL.html

[qcoderpro]

@sierdzio

I added the following two lines in the .txt file and saved the project. No errors came up:

find_package(OpenSSL)
target_link_libraries(QML_5 PRIVATE OpenSSL::SSL)

But still the project can't run successfully!

[SGaist]

Hi,

Which version of OpenSSL are you using ?

[qcoderpro]

@SGaist

I don't know! (How to know that!?)

But it's written in CMakeLists.txt:

cmake_minimum_required(VERSION 3.14)

[SGaist]

That's the minimal cmake version required to build the project.

As for OpenSSL, the installer might tell you this.
The headers of the library.

Or use QSslSocket::sslLibraryVersionString.

[qcoderpro]

@SGaist

As for OpenSSL, the installer might tell you this.
The headers of the library.

Or use QSslSocket::sslLibraryVersionString.

How to use it in my QML project?
I used it this way but that doesn't work!

Component.onCompleted: {
        console.log(QSslSocket::sslLibraryVersionString)
    }

[SGaist]

@qcoderpro said in QML Image: TLS initialization failed:

QSslSocket::sslLibraryVersionString

Use it in you main.cpp.

[qcoderpro]

@SGaist

I included these two header files:

#include <iostream>
#include <QSslSocket>

and this line in main.cpp:

std::cout<< "The openSSL version is: " <<
            QSslSocket::sslLibraryVersionString << '\n'

In return I get this warning in the Issues window and nothing related to what I foresee in Application/Compile Output windows!

warning: address of function 'QSslSocket::sslLibraryVersionString' will always evaluate to 'true'

[SGaist]

QSslSocket::sslLibraryVersionString is a static function that you have to call.

[qcoderpro]

@SGaist

Yes, I didn't notice the parentheses enough. Finally using: qInfo() << QSslSocket::sslLibraryVersionString(); I could see the result: "OpenSSL 1.1.1f 31 Mar 2020", which is very close to what the installer showed!

[SGaist]

Except it should be the j release. You should ensure that this is the one used by your application.

[qcoderpro]

@SGaist

You mean I have two files/packs installed as openSSL, one with f release and the other with j and that f release is what QtCreator is using!? So what is the problem with that f release the IDE is using and why can't it run the program by that properly?

Or probably there's a conflict between the two releases and I need to uninstall one to run the app properly! :(
But how?

[qcoderpro]

Now when I run the project, Issues, Compile Output and General Messages windows show nothing. Only Application Output shows this:
Starting ... build-QML_5-Desktop_Qt_5_15_2_MinGW_64_bit-Debug\QML_5.exe ... which shows nothing bad!

So why still nothing as output is shown? :(