I totally agree to switch to MSVC2015.
I moved to MSVC2015 last week and the compile time is shorter, so as I haven’t
found any issue, I will never back to MSVC2013.
Antonio
From: Bastien Montagne
Sent: Friday, December 2, 2016 2:44 PM
To: bf-committers@blender.org
Subject: Re:
does this mean I will be able to use pip to install things like PYTTSX or
PIL etc with pip inside a blender distro?
On Fri, Dec 2, 2016 at 2:27 AM, Dalai Felinto wrote:
> Hi there,
>
> The blendfile.py project provides a python module to read/write .blend
> files. This
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
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
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
Hi there,
The blendfile.py project provides a python module to read/write .blend
files. This project started in 2009 by Jeroen Bakker, and was later
maintained and developed further by multiple developers (Campbell
Barton, Bastien Montage, Sybren Stüvel).
Although long-lived, the library only