| Thanks to Jens and Doug for the responses. Yes, I'm developing that program. This is a program that should run on various platform, specially on large scale parallel computers. So my concern is to rely on library available on other linux machine. I'll look at common Crypto
Thanks, Bernard
On Oct 12, 2016, at 1:13 PM, Jens Alfke < email@hidden> wrote:
On Oct 12, 2016, at 10:50 AM, Doug Hill < email@hidden> wrote:
Using libraries from your local drive /usr/lib will give you the Macintosh libraries only, not necessarily what will be linked at runtime on the iOS device. e.g. ARM versions of these libraries.
Um, Bernard said he’s building for Mac, not iOS.
I don’t know why there’s a link error, but Apple has been telling us for at least ten years to avoid the system libCrypto library. IIRC the reason is that OpenSSL’s API can change incompatibly between releases. Maybe Xcode has started to enforce this by refusing to link against it?
Pretty much anything you can do with libCrypto can be done with CommonCrypto or the Security framework, so if you own the code that’s calling it, it’d be a good idea to switch over.
—Jens
Uh right, I definitely have iOS on the brain.
But I still think you shouldn't be linking against a library in your local OS system, you should probably stick with the Frameworks/Libraries in Mac OS/macOS 10.x SDK. The fact that libCrypto isn't in the macOS SDK probably indicates Apple doesn't support it.
Again, the options are to use Common Crypto as Jens suggests, or build and link against your own copy of libCrypto.
Doug Hill
|