Opened 4 years ago
Closed 4 years ago
#60897 closed defect (fixed)
caf: Should use MacPorts openssl
Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | Schamschula (Marius Schamschula) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.6.3 |
Keywords: | Cc: | ||
Port: | caf |
Description
-- Found OpenSSL: //usr/lib/libcrypto.dylib (found version "1.1.1g") CMake Error at CMakeLists.txt:625 (message): failed to compile/link against OpenSSL
This should probably be using MacPorts openssl instead.
Change History (2)
comment:1 Changed 4 years ago by Schamschula (Marius Schamschula)
comment:2 Changed 4 years ago by Schamschula (Marius Schamschula)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
Yes. The project home page didn't list any dependencies other than cmake (and Pthread). I didn't notice, as my machine picked up the MacPorts version. I assume libressl should also work, but my build machine only has openssl installed, and I can't test that.
Now, it looks like caf is also looking for curl by default and finding the version in the SDK. Unfortunately, it looks like cmake isn't finding the MacPorts version, even when given hints using configure.args. Hence, I've disabled building curl examples.