Things like

"std::istream::peek()", referenced from:
CryptoPP::FileStore::CopyRangeTo2(CryptoPP::BufferedTransformation&,
unsigned long long&, unsigned long long, std::string const&, bool) const in
libcryptopp.a(files.o)

indicate that you have C++ standard library mismatch.

So your project uses a different stdlib from your build of cryptopp. Clang
in xcode comes with 2 standard libraries: libstdc++ and libc++, those has
to be matched across ALL libs and dlls using anything from C++ at all (so
anything but pure C stuff, and not just in interface, internally too).
Because std::string is different from std::string.

For our code we wanted to use C++11 stuff, which is much better supported
in libc++ (the other one is being deprecated I think). I don't know what
your requirements are, but keep in mind that if you go to libc++, you'll
need to rebuild absolutely everything with that. In your case at least
boost, cryptopp and wxwidgets.

libstdc++ is the one that supposed to be compatible with GCC's stdlib, so
much less recompiling is required. But worse support for C++11, if that's
what you want.


On Fri, Jan 24, 2014 at 8:49 AM, Tim Burgess <[email protected]> wrote:

> OK, I get the hint - I thought that I needed to have all the libraries
>> matched.
>> I've rebuilt using make static test and incorporated the .a file into my
>> XCode 5.02 project.  The complete build log is at
>> https://dl.dropboxusercontent.com/u/29578720/Crypto.txt - the two
>> warnings about library directories are spurious - I've checked the
>> directories called in the ld line and they exist and are correct for my
>> purposes (XCode adds directories to the library search path when you
>> drag/add a library file to the project). I've removed and re-added all of
>> my required library files to ensure that the library search path is
>> correctly set, but get unknown symbol errors for the crypto++ calls (the
>> log indicates a problem with the boost library path also, but I get no
>> symbol errors for boost calls at all).
>> What else could cause unknown symbol errors in this context?
>> Cheers.
>> Tim
>>
>>
>  --
> --
> 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/groups/opt_out.
>

-- 
-- 
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/groups/opt_out.

Reply via email to