Details
-
Bug
-
Resolution: Done
-
P1: Critical
-
6.2.0
-
None
-
Ubuntu 20.04 LTS
cmake 3.19.2 from Qt online installer
g++ 9.3.0
clang 10.0.0
-
c9a96928307c1f6012d731e3a47979ca73203fe8 (qt/qtbase/dev)
Description
- Have a statically linked Qt.
I configured and built it with:/tmp/cmake-network/qt5/configure -static -release -prefix $PWD/qtbase -opensource -confirm-license -nomake tests -nomake examples && cmake --build . --parallel
- Use this to build the attached cmake project:
/tmp/cmake-network/static/qtbase/bin/qt-cmake /tmp/report/ && cmake --build .
- Run the resulting binary passing the attached certificate file:
./pem /tmp/report/qt-io.pem
You will get output like:
qt.network.ssl: No functional TLS backend was found qt.network.ssl: No functional TLS backend was found qt.network.ssl: No TLS backend is available qt.network.ssl: No functional TLS backend was found isNull(): true expiryDate(): QDateTime(Invalid)
Doing exactly the same with a non-static build of Qt will result in the output:
isNull(): false expiryDate(): QDateTime(2021-09-29 12:00:00.000 UTC Qt::UTC)
I expect the same output from a static build.
Should my CMakeLists.txt contain a mistake which causes this, please let me know.
Attachments
Issue Links
- relates to
-
QTBUG-94207 Static build fails, all platforms
-
- Closed
-