> -----Original Message----- > From: Nuno Santos [mailto:nunosan...@imaginando.pt] > Sent: Wednesday, March 02, 2016 5:22 PM > To: Koehne Kai <kai.koe...@theqtcompany.com> > Cc: interest <interest@qt-project.org> > Subject: Re: [Interest] Enabling OpenSSL on a shared build of Qt > > I think I have missed something. If it has support enabled by default why > can’t he find openssl on my system? I’m on Mac OSX 10.11.2 and I there > are this crypto and ssl libs available: > > /opt/local/lib/libcrypto.dylib > /usr/lib/libcrypto.dylib > > /opt/local/lib/libssl.dylib > /usr/lib/libssl.dylib > > Are they incompatible?
Ah, I missed to that you're talking about OS X. There the system OpenSSL version should work - though it's very old (0.9.8y IIRC). You get these warnings though because Qt checks for newer API. It's a runtime warning though, basic SSL should still work. > I would compile Qt if needed I just want to see if I can avoid it. If you do so, consider configuring with -securetransport. This let QtNetwork use Apples Secure Transport library, instead of the deprecated OpenSSL one. Regards Kai _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
