Add a new QT_NO_SSL feature macro.
authorRichard Moore <rich@kde.org>
Tue, 3 Jan 2012 14:08:03 +0000 (14:08 +0000)
committerQt by Nokia <qt-info@nokia.com>
Fri, 6 Jan 2012 10:19:23 +0000 (11:19 +0100)
commitb328e36e41dc0c529c897fe845c53be1d39424be
tree7a9e2dacda5a6ca7da6923425e793b50f908bc08
parentc25d147c4304ef85653f628259b2fa4846e1c29f
Add a new QT_NO_SSL feature macro.

At the moment users of Qt must detect if it was compiled with SSL
support by testing for QT_NO_OPENSSL. This means that any code that is
conditionally compiled this way is tied to the presence of the openssl
backend. This commit makes it possible to implement new SSL backends
during the Qt5 lifetime without breaking this code. People can still
test for QT_NO_OPENSSL if they really need openssl, but if they simply
want to know if there's SSL support at all they should use this define
instead.

In addition, this commit changes the public API headers to use the new
define.

Change-Id: Ib57a71aa65836ac9351f120a487bfeb8009d9515
Reviewed-by: Peter Hartmann <peter.hartmann@nokia.com>
configure
configure.exe
src/network/ssl/qsslcertificate.h
src/network/ssl/qsslcertificateextension.h
src/network/ssl/qsslcipher.h
src/network/ssl/qsslconfiguration.h
src/network/ssl/qsslerror.h
src/network/ssl/qsslkey.h
src/network/ssl/qsslsocket.h
tools/configure/configureapp.cpp