I still haven't figured out why this is happening, but I did figure
out a workaround. I added the following code to the top of pch.h:
#define CRYPTOPP_ENABLE_COMPLIANCE_WITH_FIPS_140_2 0
#if CRYPTOPP_ENABLE_COMPLIANCE_WITH_FIPS_140_2 == 1
#pragma message("FIPS Compliance is Enabled")
#elif CRYPTOPP_ENABLE_COMPLIANCE_WITH_FIPS_140_2 == 0
#pragma message("FIPS Compliance is Disabled")
#else
#pragma message("FIPS Compliance is Ambiguous")
#endif
This gives a warning when compiling:
c:\Libraries\cryptopp561\pch.h(5) : warning C4005:
'CRYPTOPP_ENABLE_COMPLIANCE_WITH_FIPS_140_2' : macro redefinition
command-line arguments : see previous definition of
'CRYPTOPP_ENABLE_COMPLIANCE_WITH_FIPS_140_2'
...but it does compile and works correctly. I just can't figure it
out, since I have checked and re-checked and triple checked.... to
make sure that CRYPTOPP_ENABLE_COMPLIANCE_WITH_FIPS_140_2 is NOT being
defined in the pre-processor settings of the project for either debug
or release. I can't figure out where it thinks it is being defined in
the command line. It would be nice to know what's making this happen,
but at least for now I have a workaround.
Thanks,
David
--
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.