[Interest] Qt 5.9.0 and OpenSSL 1.1.0f

[Bob Hood]

I am building Qt 5.9.0 under Windows with OpenSSL.

I have been building previous versions using OpenSSL 1.0.1h (the "heartbleed" 
patch). I am using this configurationwith Qt 5.9.0:

    Configure: configure -opensource -confirm-license -prefix
    Q:\Qt\5.9.0\64_dll -mp -release -nomake examples -no-qml-debug
    -no-compile-examples -nomake tests -openssl-linked -I
    Q:\Qt\openssl_64_dll\include -L Q:\Qt\openssl_64_dll\lib -opengl desktop
    OpenSSL path: Q:\Qt\openssl_64_dll (v1.0.1h) (linked)

and it builds without complaint, showing OpenSSL support in the diagnostic output:

    [...]
    OpenSSL ................................ yes
    Qt directly linked to OpenSSL ........ yes
    [...]

However, when I try to build Qt 5.9.0 using OpenSSL 1.1.0f (current release) 
with this configuration:

    Configure: configure -opensource -confirm-license -prefix
    Q:\Qt\5.9.0\64_dll -mp -release -nomake examples -no-qml-debug
    -no-compile-examples -nomake tests -openssl-linked -I
    Q:\Qt\openssl_64_dll_110f\include -L Q:\Qt\openssl_64_dll_110f\lib -opengl
    desktop
    OpenSSL path: Q:\Qt\openssl_64_dll_110f (v1.1.0f) (linked)

it errors out with:

    ERROR: Feature 'openssl-linked' was enabled, but the pre-condition
    '!features.securetransport && libs.openssl' failed.

Any suggestions as to a cause on this?  The SSL library names were changed for 
Windows starting with v1.1.0 (e.g., "libeay32.lib" is now "libcrypto.lib"), 
and I'm wondering if that might be the problem here.  Is the Qt 5.9.x build 
system aware of this name change?  If not, can I correct this somehow on the 
configure line?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20170531/62b13980/attachment.html>