I also noticed that when I try to build the static, non-fips, version
of cryptlib.lib with the stock .vcproj files under Windows XP with
VS2005, it gives a compiler error from integer.h. The only way I can
get it to compile is to set the CRYPTOPP_DISABLE_X86ASM flag during
compilation.

Should I apply this flag to all the configurations so that when I
build the cryptlib stub library which compliments the fips
cryptopp.dll it's built with the same options? Or should everything
build perfectly with the existing configuration?

Thanks

--~--~---------~--~----~------------~-------~--~----~
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.
-~----------~----~----~----~------~----~------~--~---

Reply via email to