Details
-
Bug
-
Resolution: Done
-
P2: Important
-
6.2.0 Beta1
-
None
-
Windows 10
Visual Studio 2019
CMake 3.20 from system
dev build of Qt 6.20 (as at 18/7/21)
-
Windows
-
91cc4fd6994701c87329de866333eb0bda0e37ef (qt/qtbase/dev) 400fe7839e50705d71066e12245d4e64fd658e67 (qt/qtbase/6.2) 90351e40fd957f70c28a3ae839feaa349f97f0b4 (qt/qtbase/6.1)
Description
When statically linking against Qt using the latest dev build as at 18/7/21 and schannel, SSL does not work with "qt.network.ssl: No TLS backend is available" and "qt.network.ssl: No functional TLS backend was found" errors. This is identical to https://bugreports.qt.io/browse/QTBUG-94108, however this does not appear to be fixed for Windows/schannel.
configure command: .\qt6\configure.bat -nomake examples -nomake tests -opensource -confirm-license -debug-and-release -static -static-runtime -schannel -prefix C:\Qt\6.2.0-dev\msvc2019_64_static -skip qtquick3d
Attachments
| For Gerrit Dashboard: QTBUG-95283 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 360878,4 | CMake: Fix incorrect default plugin conditions on Windows | dev | qt/qtbase | Status: MERGED | +2 | 0 |
| 361258,4 | CMake: Fix incorrect default plugin conditions on Windows | 6.1 | qt/qtbase | Status: MERGED | +2 | 0 |
| 361259,2 | CMake: Fix incorrect default plugin conditions on Windows | 6.2 | qt/qtbase | Status: MERGED | +2 | 0 |