Don't explicitly check for OpenSSL anymore, but rely on Qt
authorManuel Nickschas <sputnick@quassel-irc.org>
Mon, 11 Jan 2010 18:33:49 +0000 (19:33 +0100)
committerManuel Nickschas <sputnick@quassel-irc.org>
Sun, 17 Jan 2010 20:57:53 +0000 (21:57 +0100)
commitab66db150c3eadf225fab28af591ba74093950f6
tree3d2bf01220a23e3230b5b9c217d3f626e9be6169
parenteb7a1f8ffc97239e4c1f88e9da279694bba2f35a
Don't explicitly check for OpenSSL anymore, but rely on Qt

As we're not compiling against or linking to OpenSSL, but only use Qt's SSL-related
classes, it makes no sense to check for OpenSSL support ourselves. Instead, we now check
if Qt has been built with SSL support and enable our own SSL stuff in exactly this case.

This relies on Qt caring about its deps itself, though, as it already is done for the
other Qt modules.
CMakeLists.txt
cmake/modules/Qt4ConfigDependentSettings.cmake