On Sunday, 16 September 2018 03:18:39 PDT Allan Sandfeld Jensen wrote: > No, it is not possible to support both without a lot of work, and since the > problem will go away soon, it is not worth it. Loading libssl.so.1.0 before > trying libssl.so might work though, at least if any distros exist with both > libraries.
QtNetwork already does that. It loads the libssl with the full soname that it was configured with. That is provided by the macro SHLIB_VERSION_NUMBER found in the openssl/opensslv.h header. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest