[MacPorts] #53369: Qt5 : load OpenSSL dynamically using MacPorts' port:openssl

[MacPorts]

#53369: Qt5 : load OpenSSL dynamically using MacPorts' port:openssl
-------------------------+--------------------------
 Reporter:  RJVB         |      Owner:
     Type:  enhancement  |     Status:  new
 Priority:  Normal       |  Milestone:
Component:  ports        |    Version:
 Keywords:  has_patch    |       Port:  qt5; qt4-mac
-------------------------+--------------------------
 As discussed on the devel ML:

 Qt5 can either be linked statically to OpenSSL (current build approach),
 load libcrypto and libssl dynamically, or use SecureTransport.

 When using OpenSSL, the details of how the crypto and ssl functions are
 obtained are hidden from dependent applications. IOW there are no ABI
 changes when Qt is built one way or the other. I don't know if this is
 true also when changing between OpenSSL and SecureTransport but there's a
 good chance this is purely internal too.

 The jury is still out on the pros and cons of using SecureTransport, but I
 would guess that using OpenSSL means applications get security updates as
 soon as they become available through port:openssl, even when Apple
 ignores or no longer provides them.

 The only reason I can see that Qt is currently linked statically to libssl
 and libcrypto is the fact that the dynamic load procedure doesn't consider
 libraries in ${prefix}/lib . The attached patch fixes that issue by
 inserting ${prefix}/lib into the searchpath, *after* any locations that
 might be set through `DYLD_LIBRARY_PATH` and after the application's own,
 embedded Contents/Frameworks location.
 The patch evidently needs the usual post-patch reinplace polish. It is for
 Qt 5.6.2 but applies to 5.8.0RC too.


 I haven't checked but I think it should be trivial to patch Qt4 the same
 way.

--
Ticket URL: <https://trac.macports.org/ticket/53369>
MacPorts <https://www.macports.org/>
Ports system for macOS