On Thursday, 30 June 2016 14:09:27 UTC+1, Jeffrey Walton wrote: > > > > On Thursday, June 30, 2016 at 8:15:31 AM UTC-4, jean-pierre.muench wrote: >> >> [snip] >> >> There are also issues if you go too far beyond VS2010, because you'll hit >> the problems you described there. So the usual fix would be to open the >> library in VS2010 (which should work), let the tools do their upgrade job >> and then convert to VS2015 and be good. And if you don't have VS2010, you >> can also try to adapt the vs2010.zip from the current 5.6.3 to match the >> files you have. >> > Hmm. I'm not sure what issues there are. I am planning to move to Visual Studio 2015 so it looks like these issues might strike me as well.
> > Yeah, using vs2010.zip and removing the missing files is probably the way > to go given the problems we experienced when creating vs2010.zip. Also see > https://www.cryptopp.com/wiki/Visual_Studio. > > Related to VS2015, I recently came across VC++ Standalone Build Tools for > 2015 ( > http://blogs.msdn.microsoft.com/vcblog/2015/11/02/announcing-visual-c-build-tools-2015-standalone-c-tools-for-build-environments/). > > It includes the toolchain and MSBuild. > > I'm in the middle of setting it up now. If this works, I should be able to > perform VS2015 testing from the command line. I like the IDE, but I'm happy > to work in the command line, too. > > Jeff > What is the status of cryptopp on Visual Studio 2015 please? -- -- 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.
