-
Notifications
You must be signed in to change notification settings - Fork 18
No OpenSSL support built in to package #25
Comments
There is no workaround for the moment. I agree about the fact it should be configurable in the package. I'll add it as an option as soon as possible. |
@vadixidav Is it ok for you to test with Qt 5.8.0? I made the change in the testing/5.8.0 branch. It would take too long to update all the packages up to 5.7.1. |
@vadixidav Thinking about it, you don't have to wait for the build to be complete since you'll have to rebuild your own Qt with openssl support. The change is already available in my repo. Just set it up, update your conanfile and the remote reference. |
So, I have found that it is necessary to also specify |
I can't build it with or without the configure flag (
|
So, I tried using
|
I resolved this issue by adding this to
Edit: Nevermind, it only worked from the command line. Investigating more. |
Okay, I mistakenly added the above options to
Basically, the openssl dependency must be shared and without zlib when building with openssl support. |
Could it be that this is the problem with the OpenSSL lib on windows? |
QT can be built with OpenSSL support. It uses
-no-openssl
,-openssl
, and-openssl-linked
from here. The most relevant fact is that it only adds OpenSSL support if it detects an OpenSSL library to link against and OpenSSL headers, so-no-openssl
is the most important flag to control this. The package I got fromQt/5.7.1@osechet/stable
in Conan gave me a copy of QT without OpenSSL support built in:error C2039: 'sslErrors': is not a member of 'QNetworkAccessManager'
. Using OpenSSL with QT should be an option that brings OpenSSL in as a dependency. I also had OpenSSL added as a dependency, but without QT being built with the right settings it simply doesn't have the capability to use it.Is there a workaround, or can we add this to the package settings somehow?
The text was updated successfully, but these errors were encountered: