>
> Hi,
>
 
Apologies again for the time taken for me to respond to your help - I have 
a sick child at the moment, so I'm only able to work intermittently.
 
I think I need to clarify my current situation:
 
1 - My application uses Boost 1.55.0, wxWidgets 2.9.5 and Crypto++ 5.6.2;
 
2 - I can get Boost to build with clang using either of the STD libraries;
 
3 - wxWidgets only seems to build using clang with libc++ and I've received 
no suggestions from its user group on changing this situation to use 
libstdc++, so I guess I'm stuck with it;
 
3 - Crypto++ doesn't seem to build using libc++, but builds happily using 
libstdc++;
 
4 - I need to use clang instead of GCC because I found a problem with Boost 
shared pointers that could only be rectified by using either clang or GCC 
4.5 or later (this was validated by Boost development). Using the later 
versions of GCC proved not to be a solution, as its Objective-c++ 
implementation varies from Apple's and broke one of my modules, so I'm 
stuck with Apple's clang as my only viable compiler.
 
Given all this, I seem to be in a Catch-22 scenario with points 2 and 3. Am 
I correct in thinking that the offered make files would only help if I was 
mixing compilers, rather than STD libraries, or have I got the wrong end of 
the stick?
 
I'd also like to take the opportunity to thank everybody who has tried to 
help with this and for their patience in dealing with somebody at the start 
of his Mac programming learning curve.
 
Cheers.
 
Tim
 

-- 
-- 
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
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 cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to