On Thu, Jan 23, 2014 at 4:59 PM, Mouse <mouse...@gmail.com> wrote: > 4. In my experience "-std=c++11" is *not* necessary. I've put it in only > as an attempt to get compatibility between GCC-built library and > Clang-compiled application (which failed, by the way). >
I mostly agree, the issues would be If using clang you will probably require "stdlib=libc++" if linking to other libs that have been compiled with libc++ (I 'think' default since 10.8 ?) If using c++11 statements or linking to libs that have been c++11 (with clang especially) then again you need both flags. Perhaps best to do as uri suggests though. So start by compiling the most simple way make VERBOSE=1 (with no other exports) and make sure 'cryptest.exe v' runs and passes. Then worry about linking other libs later on. -- David Irvine maidsafe.net <http://www.maidsafe.net/> twitter: @metaquestions blog: http://metaquestions.me -- -- 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.
