On Aug 28, 2009, at 7:07 PM, Steven Degutis wrote:
The solution to this is pretty simple, don't link to libcrypto.
Instead, just #import in your file and
use the
CC_ prefixed functions in your app, such as CC_MD5.
Another solution is to use CDSA, which Apple provides in the Security
fram
Le 29 août 2009 à 11:27, Kyle Sluder a écrit :
On Aug 29, 2009, at 1:59 AM, Thomas Clement wrote:
Another solution is to copy the libcrypto.0.9.7.dylib from the 10.5
SDK into your project directory and link against that.
Aren't the SDK dylibs just stubs for linking purposes?
They are. B
On Aug 29, 2009, at 11:13 AM, Carl Harris wrote:
Nick Zitzmann wrote:
So if you need to use libcrypto 0.9.7, you must use the Leopard or
Tiger SDKs. You can't use the Snow Leopard SDK and libcrypto unless
you want to make your software require Snow Leopard.
Isn't it generally the case that a
On Aug 29, 2009, at 1:59 AM, Thomas Clement wrote:
Another solution is to copy the libcrypto.0.9.7.dylib from the 10.5
SDK into your project directory and link against that.
Aren't the SDK dylibs just stubs for linking purposes?
--Kyle Sluder
___
No, very much no. It's common to build against the 10.x SDK but set
the deployment target to 10.y (where y < x). This is how you take
advantage of new behavior while remaining binary compatible with older
versions.
--Kyle Sluder
___
Cocoa-dev mai
Nick Zitzmann wrote:
So if you need to use libcrypto 0.9.7, you must use the Leopard or
Tiger SDKs. You can't use the Snow Leopard SDK and libcrypto unless
you want to make your software require Snow Leopard.
Isn't it generally the case that an application built against the 10.6
SDK is going
Make sure to also use the headers from 10.5 SDK if you choose this
solution.
Le 29 août 2009 à 10:59, Thomas Clement a écrit :
Another solution is to copy the libcrypto.0.9.7.dylib from the 10.5
SDK into your project directory and link against that.
It works well.
Regards,
Thomas
On Aug
Another solution is to copy the libcrypto.0.9.7.dylib from the 10.5
SDK into your project directory and link against that.
It works well.
Regards,
Thomas
On Aug 29, 2009, at 2:07 AM, Steven Degutis wrote:
The solution to this is pretty simple, don't link to libcrypto.
Instead, just #import
The solution to this is pretty simple, don't link to libcrypto.
Instead, just #import in your file and use the
CC_ prefixed functions in your app, such as CC_MD5.
--
Steven Degutis
http://www.thoughtfultree.com/
http://www.degutis.org/
On Fri, Aug 28, 2009 at 3:41 PM, David Riggle wrote:
> I
On Aug 28, 2009, at 2:41 PM, David Riggle wrote:
Anybody know where that symbol was defined in 10.5?
I don't think it was. OpenSSL does not have a stable API, and from
what I understand, it won't until version 1.0 ships.
I really don't like this Frankenstein's SDK that I'm having to
cob
I converted my project to the 10.6 SDK, but now my app won't launch on
Leopard:
myApp[595]: dyld: Library not loaded: /usr/lib/libcrypto.0.9.8.dylib
myApp[595]: Referenced from: /Users/dave/Desktop/myApp.app/Contents/
myApp
myAppl[595]: Reason: image not found
If I select the older libcry
11 matches
Mail list logo
