Am 07.09.2015 um 17:24 schrieb Jeffrey Walton: > Hi Everyone, > > We have a new release candidate available at > https://www.cryptopp.com/cryptopp563rc1.zip. Here are the checksums: > > $ md5sum cryptopp563rc1.zip > a33dd656de4567e02e64704b92820f9f > > $ sha1sum cryptopp563rc1.zip > dd6f54fb68d4133f23dff85d0b106a1053058ad8 > > $ sha256sum cryptopp563rc1.zip > 5628e248291a8f238f0d929d7d956fb4ccf836d65958172de11488b9cd1abc4a > > RC1 performs more warning cleanup under Visual Studio. I just compiled it and was *very* impressed. The number of warnings reduced from 3.5k+ down to 5/9 :) Really good job there. Although it looks like you just suppressed them ;) > It also clears some issues raised by Enterprise Analysis (/analyze). > Finally, RC1 clears a Multiarch/Fat binary issue under OS X. > > There's a diff in the ZIP describing precisely what changed from > Crypto++ 5.6.2 (version 5.6.2 was SVN revision 541). > > Please report any problems you encounter. We still don't get a clean compile on VS 2015 though.
We get an C4589 on wait.h line 140, which complains about CryptoPP::WaitObjectsTracer not calling the constructor CryptoPP::Tracer four times, I don't know how to fix it though. We still need to clean those LNK4221s which can be done by simply adding the required line (exclude from build) to the paths in cryptlib.vcproj for all configurations of strciphr.cpp, simple.cpp, polynomi.cpp, algebra.cpp, like already done for eccrypto.cpp. It doesn't work for me doing this with an editor though so we'd have to use something like VS2005 (the least version we still support) to set the flags. We also get a strange warning on algparam.h line 35 (C4459) "declaration of 'cryptopp_assert_35' hides global declaration", there seems to be no official MS documentation about this one though. I've no clue about to fix this one as it references StringSource and fipstest.cpp line 35 which is a CRYPTOPP_COMPILE_ASSERT. I'm sad to have to tell you that the 64-bit builds of *all* projects except cryptlib (=cryptest, cryptopp) are broken and result in a bunch of "error LNK2001: unresolved external symbol ...". I suspect that dlltest works because it doesn't link any of the affected functions. The affected functions seem to be: Baseline_Add, Baseline_Sub, X86_SHA256_HashBlocks, Rijndael_Enc_AdvancedProcessBlocks, Panama_SSE2_Pull, Salsa20_OperateKeystream, GCM_AuthenticateBlocks_2K, GCM_AuthenticateBlocks_64K, Sosemanuk_OperateKeystream These may be functions that reside in the .asm files which are de facto excluded from the build by "does not participate in build" which means the assembler is not there to assemble the necessary code. Strange. IIRC past cryptopp manually called masm.exe or ml64.exe or whatever with the corresponding file... Sorry that I couldn't provide more fixes :( BR JPM > -- > -- > 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] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout. -- -- 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.
