diff options
author | Alexandru Croitor <alexandru.croitor@qt.io> | 2017-08-24 14:57:20 +0200 |
---|---|---|
committer | Alexandru Croitor <alexandru.croitor@qt.io> | 2017-08-24 14:33:32 +0000 |
commit | 84597fa46a6c0134cef514f749c3f072bfe6fe14 (patch) | |
tree | 603bc254ae8f1c2d5509a17bd57a6572e5a3bb23 /build_history/blacklist.txt | |
parent | 9ef1e16b3325239bf782ddb893cbe2b76ab4b4d7 (diff) |
Fix the chain of issues regarding QSslConfiguration
The failure was seen on Windows CI build, but was actually present on
all platforms if the QSsl checks were properly fixed, or if certain
CMake versions randomly decided to force C++11 usage.
The first issue was that QSsl wrappers were not generated on all
platforms because the C++11 standard was not forced for the
compilation tests done in the check_qt_class macro. This is a bug in
CMake, and the official way of fixing this is introduced in the yet
unreleased CMake 3.9 version.
The current fix is a workaround to explicitly pass the C++11 standard
switch to the try_compile invocation.
The next issue concerns handling of const char[] C++ types. There are
three such members in QSslConfiguration, which caused build failures
due to incorrectly generated code.
The solution is to treat "const char[]" types as "const char*" types,
which generates correct conversion code.
Tests were also added to check for such cases.
Change-Id: I874a3591dfc5f385338de7e3aff2a2c0dd2f5719
Reviewed-by: Christian Tismer <tismer@stackless.com>
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
Diffstat (limited to 'build_history/blacklist.txt')
0 files changed, 0 insertions, 0 deletions