ssl - Relation between QT_NO_SSL and QSslSocket::supportsSsl() -

there define qt_no_ssl, defined if there no ssl library found. there method qsslsocket::supportsssl().

but how these 2 related, equivalent? qt_no_ssl <=> qsslsocket::supportsssl() returns false hold or possible qt_no_ssl not defined, qsslsocket::supportsssl() returns false?

qt (at least openssl backend) can compiled:

1. with no ssl support -- qt_no_ssl defined, ssl classes not available compilation;
2. with ssl support loaded @ runtime => openssl headers must present @ compile time, qtnetwork won't link libssl/libcrypto/...; instead, dlopen libraries @ runtime looking functions needs;
3. with ssl support linked qtnetwork.

_{the reason has fact linking qtnetwork cryptographic library opens legal problems in terms of redistribution from/to us. #3 must have ssl libraries around or application won't start, if don't need ssl @ all; , qt installers can't "easily" ship ssl libraries. instead qt gets compiled in configuration #2 , you have responsability of installing openssl.}

the scenario in qt_no_ssl not defined qsslsocket::supportsssl() returns false #2 (for instance if qt fails find or load suitable ssl library).