Since I don't use clang on platforms other than OSX, I cannot tell what behavior it exhibits on iOS or Linux.
But I can tell that the OSX customizations I applied appear necessary (tested up to Mavericks 10.9.5), especially if you want to use dynamic libraries and such, and I'd greatly appreciate if they are added to the distro. Sent from my iPad > On Dec 1, 2014, at 19:12, Jeffrey Walton <[email protected]> wrote: > > >> On Tuesday, October 14, 2014 4:43:35 PM UTC-4, Mouse wrote: >> Update. Attached is the patch to cpu.h that gets crypto++-5.6.2 compile and >> run correctly under Xcode-6.0.1. Attaching my GNUmakefile diff just in case >> - it adds quite a bit of customization and support for dynamic linking under >> Mac OS X. >> >> Wei, it would be really nice if you could incorporate these changes, >> especially the GNUmakefile. It is tiresome to re-enable Mac OS X specifics >> with every release. :-) > Out of curiosity, is this a problem with Clang/OS X, or a problem with Clang > in general? > > Will the problem surface using Clang/iOS combination, or Clang/Linux? > > (Sorry to have to ask. `make test` usually works for me, so I don't see this > problem). > > 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.
