>
>On Jan 3, 2014, at 2:37 AM, Jean-Daniel Dupas <devli...@shadowlab.org>
>wrote:
>
>> The simplest advice is don't use libcrypto.
>> 
>> If you just need simple functionality, you may have a look at the
>>CommonCrypto API which is partially available on 10.5 ( I think Digest
>>and Cryptors where available at this time).
>> 
>> If you need something more complex, you should use the Security
>>framework, unfortunately the whole 10.5 API (CDSA) has been deprecated
>>in favor of a cleaner but incompatible API.
>> 
>> So you will have to write the code twice if you want to support 10.5
>>and be futur proof.
>
>Unfortunately, if you're using asymmetric encryption, you have to use the
>deprecated CDSA APIs, since (AFAIK) the newer APIs don't support it.
>
>Charles

I had the same problem with libnetsnmp and solved it with a Run Script
build phase.  The linker puts the versioned dylib in the executable even
though you include the non-versioned dylib, this switches the versioned
back to non-versioned.

install_name_tool -change ³<versioned dylib>² ³<non-versioned dylib>"
"$TARGET_BUILD_DIR/$EXECUTABLE_PATH²

In my case: install_name_tool -change "/usr/lib/libnetsnmp.15.dylib"
"/usr/lib/libnetsnmp.dylib" "$TARGET_BUILD_DIR/$EXECUTABLE_PATH"

Hope this helps,

Dave



_______________________________________________

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to