Am not at all a windows specialist, but on a general point of view, I totally agree that maintaining a single build env for windows will help everybody save time for more interesting things, reduce occurrences of libs version mismatch between build env, and… use a more modern and standard-compliant compiler afaik.
So unless we do have any serious known issue with MSVC2015, I see no reason not to switch to it and deprecate (fade into oblivion) MSVC2013. ;) Just my two cents Le 02/12/2016 à 14:21, Sergey Sharybin a écrit : > Hey everyone, > > We've got MSVC 2015 libraries and buildbot for quite some time now. While > there are some compilation errors time to time on buildbot, they don't seem > to be MSVC 2015 specific at all. > > Is there any reason NOT to make MSVC 2015 a default one for Blender? This > will include: > > - Removing MSVC 2013 builders from buildbot. As a benefit users wouldn't be > confused whether they should go with 2013 or 2015 builds. > - Moving focus to MSVC 2015 libraries, which will save us time form > maintaining and testing MSVC 2013 libraries. > - If nobody from community steps up for the 2013 libraries maintenance > those libraries will fade out naturally as it happened when we switched > from 2008 to 2013. > > Any thoughts? > _______________________________________________ Bf-committers mailing list [email protected] https://lists.blender.org/mailman/listinfo/bf-committers
