OSX 10.11 no openssl

[bensuffolk]

I have just upgraded my dev environment to 10.11 and am now unable to compile my application that uses AquaticPrime as the openssl headers are no longer included in the SDK.

[marcvanolmen]

I just noticed the same after upgrading to Xcode 7 (on 10.10 machine) because only 10.11 sdk is used: There are several options to resolve this:

• use homebrew for example to compile openssl and include it in the project and link to the static library. (probably easiest route)
• Or upgrade the code itself and upgrade to the newest API's from apple, for example use this sample code:
  https://developer.apple.com/library/prerelease/mac/samplecode/CryptoCompatibility/Listings/Operations_QCCAESPadCryptor_m.html#//apple_ref/doc/uid/DTS40013654-Operations_QCCAESPadCryptor_m-DontLinkElementID_8

[DouglasHeriot]

My solution is to include my own build of openssl. I used this script I found to build it: https://gist.github.com/letiemble/6710405

Note that you have to be careful just including stuff from homebrew – it’s really not designed for that. You need to set the -mmacosx-version-min=10.9 compiler flag to whatever OS you want to support. Otherwise, users with older OSs may have issues! (ie. in the past I shipped a beta build with a homebrew library, which used more modern SSE instructions than my minimum supported OS’s minimum hardware supported)