I find the excessive customization that Eugene did quite unnecessary, and probably harmful: there is no reason to enforce the minimal version of Mac OS X, there is no need to enforce c++11 standard, there is no need to explicitly point at MacOSX10.7.sdk, etc.
Simplicity is our friend. :-) And again, compiling Crypto++ has been working OK for me since Leopard, with different compilers including native. The GNUmakefile that I attached previously, works fine with gcc48, clang-3.3, and clang-3.4. I used it with the native clang (from Xcode package), but don't remember whether I did anything to it (and if I did - it was *surely* less drastic than the patch you posted). TNX! P.S. Eugene, I wonder what's the reason for switching from AR to LIBTOOL...? -- -- 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.
