On Apr 12, 2017, at 8:46 PM, Richard Hipp <d...@sqlite.org> wrote: > OK, can you suggest a fix for getting the build to work correctly on > your machine?
1) Try to convince Apple to provide OpenSSL header files - perhaps by convincing them to implement the OpenSSL API atop their own SSL code, as I think they really want everybody to use their SSL code, the fact that this isn't going to work well with all the non-macOS-specific free software out there notwithstanding. 2) Try to build on a machine running a version of the OS that has the OpenSSL headers (meaning "not Sierra, and possibly not some earlier versions" - I don't remember whether it was Sierra or El Capitan or Yosemite or even earlier when they got rid of the OpenSSL headers). 3) Ship it as an installer package that includes both the Fossil binary and a version of OpenSSL, and have the package install the binary in /usr/local/bin and the OpenSSL libraries in /usr/local/lib. 4) Try to use Apple's APIs on macOS and OpenSSL everywhere else (if that's possible, and if Apple's APIs are available on all the OS versions you want to support). 5) Abandon the attempt to provide binaries and require that people build from source. I'm getting it to work on my machine by just building and installing OpenSSL from source, and then building Fossil from source. I suspect 1) isn't going to work, and 4) might be a pain. (I may try to dive into that pool of pain anyway with tcpdump, which uses OpenSSL APIs for some crypto purposes.) _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
