I agree, let's do this ASAP.
On 2 Dec 2016 2:21 pm, "Sergey Sharybin" wrote:
> 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
-committers] Promoting MSVC 2015 builds as official
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
Sounds good to me!
--Ray
On 12/2/2016 6:21, Sergey Sharybin wrote:
> 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 reas
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-compl
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
