The GNUmakefile supplied with Crypto++ detects that GNU assembler 2.10 or later isn't available on OS X and disables the inline assembly. Alexis, you need to add the compiler flag -DCRYPTOPP_DISABLE_ASM yourself if you're bypassing the makefile.
-------------------------------------------------- From: "Geoff Beier" <[EMAIL PROTECTED]> Sent: Wednesday, September 03, 2008 5:22 AM To: "alexis.oldroyd" <[EMAIL PROTECTED]> Cc: "Crypto++ Users" <[EMAIL PROTECTED]> Subject: Re: Building under Mac > > On Tue, Sep 2, 2008 at 1:29 PM, alexis.oldroyd <[EMAIL PROTECTED]> > wrote: >> >> I've imported CryptoPP into XCode and am trying to compile it as a >> "BSD Static Library" project. I have it set to use GCC 4.2, but I also >> tried with the default 4.0. >> > > Disclaimer: I'm not shipping anything with crypto++ to end users on > the mac right now, so I have not concerned myself with such packaging > niceties as universal binaries. That said, I use it on the mac > semi-regularly and have never tried to build it the way you describe. > I always just run "make libcryptopp.a" from the directory where I've > unzipped. For recent versions of crypto++ and recent versions of OS X > that just works. > > HTH, > > Geoff > > > --~--~---------~--~----~------------~-------~--~----~ 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. -~----------~----~----~----~------~----~------~--~---
