[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:
Resolution:                |   Keywords:  has_patch
      Port:  qt5; qt4-mac  |
---------------------------+-----------------------

Comment (by RJVB):

 I have asked the question on Qt's mailing list. I do notice that the
 default build on Linux uses runtime loading of OpenSSL, and no
 distribution I know of excludes Qt or Qt Creator from binary distribution
 because of this. Nor the Qt company themselves, for that matter.

 The GNU FAQ talks about statically vs. dynamically linked, and considers
 both the identical from a licensing viewpoint. That affects -openssl-
 linked, but shouldn't affect runtime loading because that is yet something
 else. It looks like OpenSSL headers are being included, though.
 The final link isn't clear about whether it considers linking or using
 dlopen+dlsym, but probably the former; it also talks about redistributing
 the source code and the kind of license conflict you can run into. That is
 a very different problem than the question whether or not MacPorts can
 make a binary build of something available.
 Finally, the post on the ML is Josh's opinion based on his interpretation
 of the most restrictive viewpoint.

 If that opinion is law here, then we're out of luck unless we force Qt to
 use the system OpenSSL libraries. There might be a hole in the net though:
 OS X ships libssl and libcrypto, and the runtime loading process *will*
 find those exact libraries, even with my patch, if port:openssl isn't
 active:

 {{{
 However, as a
   special exception, the source code distributed need not include
   anything that is normally distributed (in either source or binary
   form) with the major components (compiler, kernel, and so on) of the
   operating system on which the executable runs,
 }}}

 It's nitpicking, but this should mean that we ought to be safe if
 - Qt only declares a build dependency on port:openssl
 - Qt Creator doesn't declare any dependency on port:openssl

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