On Tuesday, December 8, 2015 at 6:02:16 PM UTC-5, Arthur Coleman wrote:
>
> I loaded the following code into an XCode 7.1.1 project added the location 
> of crypto++ headers and libraries to their respective search paths.  I then 
> added the crypto++ libraries libcryptopp.a and libcryptopp.dyld Link Binary 
> With Libraries list.  The code compiled successfully and began running.  I 
> then receive the following error:
>
> *dyld: Library not loaded: libcryptopp.dylib*
>
> *  Referenced from: 
> /Users/arthur/Library/Developer/Xcode/DerivedData/cryptoppAES-bbtucachjqqaeediqkjywpllseec/Build/Products/Debug/cryptoppAES*
>
> *  Reason: image not found*
>
>
It looks like the shared object is not being copied under Xcode.

I think you have three choices. First, delete the shared object so that you 
link against the static library. Second, follow something like 
https://stackoverflow.com/questions/20092886/image-not-found-error-while-using-custom-framework
 
. Third, set DYLD_FALLBACK_LIBRARY_PATH 
(https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man1/dyld.1.html).

The first is a pretty good choice on Apple platforms, especially if you are 
building for iOS. Apple linkers always link to the shared object, even 
though you try to force static linking. Its a problem on iOS because most 
versions of iOS don't allow dynamic linking for user code.

I generally don't use Xcode, so maybe someone else will have other 
suggestions.

Jeff

-- 
-- 
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to [email protected].
More information about Crypto++ and this group is available at 
http://www.cryptopp.com.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to