On 20/08/2009, at 10:52 AM, Steve Mykytyn wrote:
Suggestions?
I link to libcrypto simply by adding a -libcrypto to my other linker
flags in the project settings. I don't have to include any paths or
frameworks or anything, and it works.
--Graham
On 20/08/2009, at 4:09 PM, Graham Cox wrote:
On 20/08/2009, at 10:52 AM, Steve Mykytyn wrote:
Suggestions?
I link to libcrypto simply by adding a -libcrypto to my other
linker flags in the project settings. I don't have to include any
paths or frameworks or anything, and it works.
On Aug 19, 2009, at 5:52 PM, Steve Mykytyn wrote:
The older machine does not have /usr/lib/libcrypto.0.9.x.dylib, it
has /usr/lib/libcrypto.0.9.y.dylib, which is where the alias
resolves, but somehow the app does not get it right.
Note that it's a symlink, not an alias...
I have
I have an app that needs to work across recent OS X versions. It
links in the libcrypto.dylib, which is of course an alias.
Path: /usr/lib/libcrypto.dylib
Full Path: /usr/lib/libcrypto.0.9.x.dylib (anonymized to respect
NDAs)
App works fine on the dev machine with the newer OS X
