[snip]
>
> Chiming in, yes, I just pulled from master (hadn't updated for about a
> month), did full 32 and 64 -bit builds of cryptest, and all is good -
> not a single warning or error, and all tests pass - thanks, Jeff and
> all who contributed to this level of code cleanliness and compatibility!
>
> That said, it would be nice if we could move into the present, and use
> vs2015 as a base (vs2010, really?) for Windows builds - but I know not
> everyone agrees on this point. ;)
VS2010 and VS2015 basically have the same (project- and solution-)
format. VS2015 adds a few new fancy switches (like CFG) but nothing of
real and hard importance.
So it's really a matter of "letting the IDE switch the compiler version
from v100 to v140", so let's just stay at the older version for now.
>
> It is *free* (the "Community Edition"), and after the recently
> ("Update 3") replaced codegen, generates really smart and nice code -
> note that I am only paying attention to the 64-bit Intel support here.
>
It is not free as in "you don't have to pay anything", you pay with
having to sign in to your MS account, which has already trapped some of
us here. And if you're a developer who (for whatever reason) doesn't
qualify for the community edition, you have to pay several hundred USD
to get the pro version, which is not a dependency or a requirement we
want to impose on people.

TL;DR: As far as I understand current consensus we won't upgrade from
VS2010 project files away, because it's not enough of a benefit for too
much potential headache for the users.

BR

JPM

-- 
-- 
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
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 cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to