[Interest] Enabling OpenSSL on a shared build of Qt

Thiago Macieira thiago.macieira at intel.com
Thu Mar 3 00:29:16 CET 2016


On quarta-feira, 2 de março de 2016 23:15:09 PST Nuno Santos wrote:
> cat out | grep ssl
> loaded library "/usr/lib/libssl.dylib"
> qt.network.ssl: QSslSocket: cannot resolve SSL_set_psk_client_callback
> qt.network.ssl: QSslSocket: cannot resolve TLSv1_1_client_method
> qt.network.ssl: QSslSocket: cannot resolve TLSv1_2_client_method
> qt.network.ssl: QSslSocket: cannot resolve TLSv1_1_server_method
> qt.network.ssl: QSslSocket: cannot resolve TLSv1_2_server_method
> qt.network.ssl: QSslSocket: cannot resolve SSL_select_next_proto
> qt.network.ssl: QSslSocket: cannot resolve SSL_CTX_set_next_proto_select_cb
> qt.network.ssl: QSslSocket: cannot resolve SSL_get0_next_proto_negotiated
> qt.network.ssl: QSslSocket: cannot call unresolved function
> SSL_get0_next_proto_negotiated qt.network.ssl: QSslSocket: cannot call
> unresolved function SSL_get0_next_proto_negotiated
> 
> Can’t find anything that can help.
> 
> If it is trying to load older libs what should be my call here? Delete old
> libs and get new ones?

A solution: set DYLD_LIBRARY_PATH to /usr/local/lib

A better solution: copy the two libraries to your application's 
	<bundle>/Contents/Frameworks

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center




More information about the Interest mailing list