On 04/13/17 13:25, Stephan Beal wrote: >>>> did anyone come up with a solution to SSL on Mac problem? >>> Can you remind us what the "SSL on Mac" problem is? >> >> I believe the issue stems from that Apple decided that OpenSSL is >> uncool and everyone should use their system (Objective-C) library >> instead. The dynamic OpenSSL libraries remain in the system for >> compatibility, but they no longer include the headers -- so when you >> build fossil on new:ish Macs (read: XCode), build systems tend to find >> non-system instances of OpenSSL and use them instead. > > What if, instead of #including the openssl headers, fossil simply declares > the few external interfaces it uses in its own sources?
That's one possible solution, but imho it's a pretty ugly band-aid. I think it's better to go back to the original idea of using statically-linked libraries for the pre-built binaries. That way when Apple decide to eliminate the dynamic libraries as well (not that I think they can do that any time soon) the monolithic fossil binary will continue to work. -- Kind regards, Jan Danielsson _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
