Re: [Bf-committers] Library updates for Blender 2.8

[Ray Molenkamp]

We'll get going on this then, there's one lib I'd like some clarification on
arto requested boost 1.66 on irc, not a problem on windows (I'd welcome an
updated version, but do not require it), but how are the linux guys feeling
about bumping the boost version?

--Ray


On 8/8/2018 9:54 AM, Brecht Van Lommel wrote:
> Hi all,
>
> Regarding how to get this moving further, I had a quick talk with Sergey.
> To avoid the Linux part being a bottleneck, I suggest to update the Windows
> and macOS libraries as soon as they are ready, and commit the build
> environment CMake changes alongside them. It's not a big deal if the
> platform versions are out of sync for a bit, and Sergey can do the
> corresponding updates for Linux when he has time.
>
> So Ray and Arto can just coordinate committing these changes amongst
> themselves. If any C/C++ code needs to change we can use #ifdef's, which we
> want anyway in case Linux users are compiling against different library
> versions.
>
> Thanks,
> Brecht.
>
> On Sat, Aug 4, 2018 at 9:01 PM Bastien Montagne 
> wrote:
>
>> Don’t think we are in urgent hurry here, we can give it a few more weeks
>> and see whether 3.7.1 emerges in time for us (would say dead line for
>> libs update would be end of September?)
>>
>>
>> On 03/08/2018 10:57, Sergey Sharybin wrote:
>>> One thing which is raising my attention in 3.7.1 release log is:
>>>
>>> - Fixed a performance regression for reading streams with tarfile.
>>>
>>> Also, 3.7.1 is planned to be released soon-ish? Their original plan
>>> actually mentions July, not sure what is the updated planning. Are we
>>> really in a hurry for this update?
>>>
>>> On Fri, Aug 3, 2018 at 10:46 AM Sybren A. Stüvel 
>> wrote:
 On 23/07/2018 19:43, Brecht Van Lommel wrote:
> * Python 3.7.0 (or should we wait until there is a 3.7.1 or so with
> bugfixes?)
 Let's go to 3.7.0, unless somebody already knows of actual bugs that'll
 influence our use.

 Sybren

 ___
 Bf-committers mailing list
 Bf-committers@blender.org
 https://lists.blender.org/mailman/listinfo/bf-committers

>> ___
>> Bf-committers mailing list
>> Bf-committers@blender.org
>> https://lists.blender.org/mailman/listinfo/bf-committers
>>
> ___
> Bf-committers mailing list
> Bf-committers@blender.org
> https://lists.blender.org/mailman/listinfo/bf-committers

___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Library updates for Blender 2.8

[Brecht Van Lommel]

Hi all,

Regarding how to get this moving further, I had a quick talk with Sergey.
To avoid the Linux part being a bottleneck, I suggest to update the Windows
and macOS libraries as soon as they are ready, and commit the build
environment CMake changes alongside them. It's not a big deal if the
platform versions are out of sync for a bit, and Sergey can do the
corresponding updates for Linux when he has time.

So Ray and Arto can just coordinate committing these changes amongst
themselves. If any C/C++ code needs to change we can use #ifdef's, which we
want anyway in case Linux users are compiling against different library
versions.

Thanks,
Brecht.

On Sat, Aug 4, 2018 at 9:01 PM Bastien Montagne 
wrote:

> Don’t think we are in urgent hurry here, we can give it a few more weeks
> and see whether 3.7.1 emerges in time for us (would say dead line for
> libs update would be end of September?)
>
>
> On 03/08/2018 10:57, Sergey Sharybin wrote:
> > One thing which is raising my attention in 3.7.1 release log is:
> >
> > - Fixed a performance regression for reading streams with tarfile.
> >
> > Also, 3.7.1 is planned to be released soon-ish? Their original plan
> > actually mentions July, not sure what is the updated planning. Are we
> > really in a hurry for this update?
> >
> > On Fri, Aug 3, 2018 at 10:46 AM Sybren A. Stüvel 
> wrote:
> >
> >> On 23/07/2018 19:43, Brecht Van Lommel wrote:
> >>> * Python 3.7.0 (or should we wait until there is a 3.7.1 or so with
> >>> bugfixes?)
> >> Let's go to 3.7.0, unless somebody already knows of actual bugs that'll
> >> influence our use.
> >>
> >> Sybren
> >>
> >> ___
> >> Bf-committers mailing list
> >> Bf-committers@blender.org
> >> https://lists.blender.org/mailman/listinfo/bf-committers
> >>
> >
>
> ___
> Bf-committers mailing list
> Bf-committers@blender.org
> https://lists.blender.org/mailman/listinfo/bf-committers
>
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Library updates for Blender 2.8

[Bastien Montagne]

Don’t think we are in urgent hurry here, we can give it a few more weeks 
and see whether 3.7.1 emerges in time for us (would say dead line for 
libs update would be end of September?)



On 03/08/2018 10:57, Sergey Sharybin wrote:

One thing which is raising my attention in 3.7.1 release log is:

- Fixed a performance regression for reading streams with tarfile.

Also, 3.7.1 is planned to be released soon-ish? Their original plan
actually mentions July, not sure what is the updated planning. Are we
really in a hurry for this update?

On Fri, Aug 3, 2018 at 10:46 AM Sybren A. Stüvel  wrote:


On 23/07/2018 19:43, Brecht Van Lommel wrote:

* Python 3.7.0 (or should we wait until there is a 3.7.1 or so with
bugfixes?)

Let's go to 3.7.0, unless somebody already knows of actual bugs that'll
influence our use.

Sybren

___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers





___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Library updates for Blender 2.8

[Sergey Sharybin]

One thing which is raising my attention in 3.7.1 release log is:

- Fixed a performance regression for reading streams with tarfile.

Also, 3.7.1 is planned to be released soon-ish? Their original plan
actually mentions July, not sure what is the updated planning. Are we
really in a hurry for this update?

On Fri, Aug 3, 2018 at 10:46 AM Sybren A. Stüvel  wrote:

> On 23/07/2018 19:43, Brecht Van Lommel wrote:
> > * Python 3.7.0 (or should we wait until there is a 3.7.1 or so with
> > bugfixes?)
>
> Let's go to 3.7.0, unless somebody already knows of actual bugs that'll
> influence our use.
>
> Sybren
>
> ___
> Bf-committers mailing list
> Bf-committers@blender.org
> https://lists.blender.org/mailman/listinfo/bf-committers
>


-- 
With best regards, Sergey Sharybin
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Library updates for Blender 2.8

[Sybren A . Stüvel]

On 23/07/2018 19:43, Brecht Van Lommel wrote:
> * Python 3.7.0 (or should we wait until there is a 3.7.1 or so with
> bugfixes?)

Let's go to 3.7.0, unless somebody already knows of actual bugs that'll
influence our use.

Sybren

___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Library updates for Blender 2.8

[Brecht Van Lommel]

Freetype definitely needs an upgrade as well it seems. Especially after the
latest text hinting changes it the old freetype 2.6.3 we use gives very
different results than the latest 2.9.1.

On Thu, Jul 26, 2018 at 7:32 PM Ray Molenkamp  wrote:

> see inline comments
>
>
> On 7/26/2018 10:21 AM, Brecht Van Lommel wrote:
> > I think it would be great to have all these libraries updated, especially
> > the ones with CVEs.
> >
> > * Blosc: definitely need to upgrade one to fix GCC build issues
> I  marked the upgrade to latest, the minimum we need is 1.8.1 which
> already 2+ years old
> seems silly to upgrade to an already ancient version.
>
> > * clew/cuew: I wonder if we even need OpenCL/CUDA support in OpenSubdiv,
> > maybe OpenGL is enough..
> unsure, sergey would probably know better here, cuda will be problematic
> either way
> with the fighting between nvcc and the msvc compiler version that it may
> or may not
> like.  it's currently disabled because of that and I don't think anyone
> noticed?
>
> > * flexbison/schroendinger/lapack: seems fine to remove
> Marked for removal
> > * openjpeg: don't think there is a good reason to have it in extern/
> > anymore, would be happy to see patch to remove it from there
> I have brought this up in the past, and sergey seemed very passionate
> about keeping
> it there.
>
>
> >
> > I guess most of these are relatively easy with a tweak to versions.cmake,
> > not sure how difficult it is on Linux.
> Relativity easy , we just need to pay attention to that when we change a
> lib we also
> need to rebuild the libs upstream from it even if their version hasn't
> changed
> (we've run into some weird oiio issues in the past due to a libpng upgrade)
>
> just follow this 'easy' chart and it'll be fine!
>
> http://www.lazydodo.com/tmp/blender_externals.png
>
> --Ray
> >
> > On Mon, Jul 23, 2018 at 9:54 PM Ray Molenkamp  wrote:
> >
> >> There's quite a few libraries we build for the various platforms
> >> (57 by the last count) and it's not always clear who the module
> >> owner is and who is supposed to ask for newer versions of certain
> >> libs.
> >>
> >> I took a quick survey of the versions we use and the latest versions
> >> available. (based on build_files\build_environment\cmake\versions.cmake)
> >>
> >>
> >>
> https://docs.google.com/spreadsheets/d/e/2PACX-1vRnu75FDmw8NvbJiH9hjrGNBvrwXU9ocWWMCWZY0ISwcfLOnL7Ep1z67Y5FpN_TaI0QRwbPR2KmrQie/pubhtml?gid=0=true
> >>
> >> (or in case the email ruins the long link: https://tinyurl.com/y9st4fyt
> )
> >>
> >> There are several libs with known CVE's, personally I would prefer
> >> to upgrade those to the latest versions (most seem low risk upgrades)
> >> but for everything else I really have no strong opinion.
> >>
> >> Any module owner that wants edit rights, please poke me (email/irc) and
> >> I'll get you an editable link.
> >>
> >> --Ray
> >>
> >>
> >> On 7/23/2018 11:43 AM, Brecht Van Lommel wrote:
> >>> Hi all,
> >>>
> >>> It's been a while since we updated libraries, and with the upgrade to
> >>> Visual Studio 2017 this has now become easier on Windows as well. Since
> >> the
> >>> platform maintainers have time now to do updates, let's try to get this
> >> in
> >>> motion.
> >>>
> >>> Some of the latest library versions need C++11, I also propose we
> require
> >>> C++11 in master. This mostly involves removing the WITH_CXX1 option and
> >>> code cleanups for STL data types compatibility.
> >>>
> >>> For libraries, these are the ones I know of. Let us know if any other
> >>> library updates are needed.
> >>>
> >>> * OSL, LLVM, OIIO: so we no longer need a really old LLVM version.
> >>> https://developer.blender.org/D3398
> >>> https://developer.blender.org/D2915
> >>>
> >>> * OpenVDB 5.1.0: so we can read files written by other applications
> that
> >>> have OpenVDB 5.x.
> >>>
> >>> * Python 3.7.0 (or should we wait until there is a 3.7.1 or so with
> >>> bugfixes?)
> >>>
> >>> * OpenSubdiv: this will need to include a number of Sergey's bugfixes,
> >> the
> >>> revision needed is not known (or doesn't exist) yet.
> >>>
> >>> Thanks,
> >>> Brecht.
> >>> ___
> >>> Bf-committers mailing list
> >>> Bf-committers@blender.org
> >>> https://lists.blender.org/mailman/listinfo/bf-committers
> >> ___
> >> Bf-committers mailing list
> >> Bf-committers@blender.org
> >> https://lists.blender.org/mailman/listinfo/bf-committers
> >>
> > ___
> > Bf-committers mailing list
> > Bf-committers@blender.org
> > https://lists.blender.org/mailman/listinfo/bf-committers
>
> ___
> Bf-committers mailing list
> Bf-committers@blender.org
> https://lists.blender.org/mailman/listinfo/bf-committers
>
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Library updates for Blender 2.8

[Ray Molenkamp]

see inline comments


On 7/26/2018 10:21 AM, Brecht Van Lommel wrote:
> I think it would be great to have all these libraries updated, especially
> the ones with CVEs.
>
> * Blosc: definitely need to upgrade one to fix GCC build issues
I  marked the upgrade to latest, the minimum we need is 1.8.1 which already 2+ 
years old
seems silly to upgrade to an already ancient version.

> * clew/cuew: I wonder if we even need OpenCL/CUDA support in OpenSubdiv,
> maybe OpenGL is enough..
unsure, sergey would probably know better here, cuda will be problematic either 
way
with the fighting between nvcc and the msvc compiler version that it may or may 
not
like.  it's currently disabled because of that and I don't think anyone noticed?

> * flexbison/schroendinger/lapack: seems fine to remove
Marked for removal
> * openjpeg: don't think there is a good reason to have it in extern/
> anymore, would be happy to see patch to remove it from there
I have brought this up in the past, and sergey seemed very passionate about 
keeping
it there.


>
> I guess most of these are relatively easy with a tweak to versions.cmake,
> not sure how difficult it is on Linux.
Relativity easy , we just need to pay attention to that when we change a lib we 
also
need to rebuild the libs upstream from it even if their version hasn't changed
(we've run into some weird oiio issues in the past due to a libpng upgrade)

just follow this 'easy' chart and it'll be fine!

http://www.lazydodo.com/tmp/blender_externals.png

--Ray
>
> On Mon, Jul 23, 2018 at 9:54 PM Ray Molenkamp  wrote:
>
>> There's quite a few libraries we build for the various platforms
>> (57 by the last count) and it's not always clear who the module
>> owner is and who is supposed to ask for newer versions of certain
>> libs.
>>
>> I took a quick survey of the versions we use and the latest versions
>> available. (based on build_files\build_environment\cmake\versions.cmake)
>>
>>
>> https://docs.google.com/spreadsheets/d/e/2PACX-1vRnu75FDmw8NvbJiH9hjrGNBvrwXU9ocWWMCWZY0ISwcfLOnL7Ep1z67Y5FpN_TaI0QRwbPR2KmrQie/pubhtml?gid=0=true
>>
>> (or in case the email ruins the long link: https://tinyurl.com/y9st4fyt )
>>
>> There are several libs with known CVE's, personally I would prefer
>> to upgrade those to the latest versions (most seem low risk upgrades)
>> but for everything else I really have no strong opinion.
>>
>> Any module owner that wants edit rights, please poke me (email/irc) and
>> I'll get you an editable link.
>>
>> --Ray
>>
>>
>> On 7/23/2018 11:43 AM, Brecht Van Lommel wrote:
>>> Hi all,
>>>
>>> It's been a while since we updated libraries, and with the upgrade to
>>> Visual Studio 2017 this has now become easier on Windows as well. Since
>> the
>>> platform maintainers have time now to do updates, let's try to get this
>> in
>>> motion.
>>>
>>> Some of the latest library versions need C++11, I also propose we require
>>> C++11 in master. This mostly involves removing the WITH_CXX1 option and
>>> code cleanups for STL data types compatibility.
>>>
>>> For libraries, these are the ones I know of. Let us know if any other
>>> library updates are needed.
>>>
>>> * OSL, LLVM, OIIO: so we no longer need a really old LLVM version.
>>> https://developer.blender.org/D3398
>>> https://developer.blender.org/D2915
>>>
>>> * OpenVDB 5.1.0: so we can read files written by other applications that
>>> have OpenVDB 5.x.
>>>
>>> * Python 3.7.0 (or should we wait until there is a 3.7.1 or so with
>>> bugfixes?)
>>>
>>> * OpenSubdiv: this will need to include a number of Sergey's bugfixes,
>> the
>>> revision needed is not known (or doesn't exist) yet.
>>>
>>> Thanks,
>>> Brecht.
>>> ___
>>> Bf-committers mailing list
>>> Bf-committers@blender.org
>>> https://lists.blender.org/mailman/listinfo/bf-committers
>> ___
>> Bf-committers mailing list
>> Bf-committers@blender.org
>> https://lists.blender.org/mailman/listinfo/bf-committers
>>
> ___
> Bf-committers mailing list
> Bf-committers@blender.org
> https://lists.blender.org/mailman/listinfo/bf-committers

___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Library updates for Blender 2.8

[Brecht Van Lommel]

install_deps.sh will be updated with the new versions.

On Thu, Jul 26, 2018 at 6:30 PM Eugenio Pignataro 
wrote:

> Hi guys.
> We will have some like install_deps.sh?
>
> THANKS!
>
> Untitled Document
>
> Eugenio Pignataro
> Drawing & Digital Art.
> ---
> Site: www.oscurart.com.ar
> Reel: vimeo.com/92253804
> BlenderNetwork: https://www.blendernetwork.org/eugenio-pignataro
> Email: i...@oscurart.com.ar
> Phone: 54 15 5177 4936
> Skype: info_28795
> HangOut: oscurartgt...@gmail.com
> On 26/07/18 13:21, Brecht Van Lommel wrote:
> > I think it would be great to have all these libraries updated, especially
> > the ones with CVEs.
> >
> > * Blosc: definitely need to upgrade one to fix GCC build issues
> > * clew/cuew: I wonder if we even need OpenCL/CUDA support in OpenSubdiv,
> > maybe OpenGL is enough..
> > * flexbison/schroendinger/lapack: seems fine to remove
> > * openjpeg: don't think there is a good reason to have it in extern/
> > anymore, would be happy to see patch to remove it from there
> >
> > I guess most of these are relatively easy with a tweak to versions.cmake,
> > not sure how difficult it is on Linux.
> >
> >
> > On Mon, Jul 23, 2018 at 9:54 PM Ray Molenkamp  wrote:
> >
> >> There's quite a few libraries we build for the various platforms
> >> (57 by the last count) and it's not always clear who the module
> >> owner is and who is supposed to ask for newer versions of certain
> >> libs.
> >>
> >> I took a quick survey of the versions we use and the latest versions
> >> available. (based on build_files\build_environment\cmake\versions.cmake)
> >>
> >>
> >>
> https://docs.google.com/spreadsheets/d/e/2PACX-1vRnu75FDmw8NvbJiH9hjrGNBvrwXU9ocWWMCWZY0ISwcfLOnL7Ep1z67Y5FpN_TaI0QRwbPR2KmrQie/pubhtml?gid=0=true
> >>
> >> (or in case the email ruins the long link: https://tinyurl.com/y9st4fyt
> )
> >>
> >> There are several libs with known CVE's, personally I would prefer
> >> to upgrade those to the latest versions (most seem low risk upgrades)
> >> but for everything else I really have no strong opinion.
> >>
> >> Any module owner that wants edit rights, please poke me (email/irc) and
> >> I'll get you an editable link.
> >>
> >> --Ray
> >>
> >>
> >> On 7/23/2018 11:43 AM, Brecht Van Lommel wrote:
> >>> Hi all,
> >>>
> >>> It's been a while since we updated libraries, and with the upgrade to
> >>> Visual Studio 2017 this has now become easier on Windows as well. Since
> >> the
> >>> platform maintainers have time now to do updates, let's try to get this
> >> in
> >>> motion.
> >>>
> >>> Some of the latest library versions need C++11, I also propose we
> require
> >>> C++11 in master. This mostly involves removing the WITH_CXX1 option and
> >>> code cleanups for STL data types compatibility.
> >>>
> >>> For libraries, these are the ones I know of. Let us know if any other
> >>> library updates are needed.
> >>>
> >>> * OSL, LLVM, OIIO: so we no longer need a really old LLVM version.
> >>> https://developer.blender.org/D3398
> >>> https://developer.blender.org/D2915
> >>>
> >>> * OpenVDB 5.1.0: so we can read files written by other applications
> that
> >>> have OpenVDB 5.x.
> >>>
> >>> * Python 3.7.0 (or should we wait until there is a 3.7.1 or so with
> >>> bugfixes?)
> >>>
> >>> * OpenSubdiv: this will need to include a number of Sergey's bugfixes,
> >> the
> >>> revision needed is not known (or doesn't exist) yet.
> >>>
> >>> Thanks,
> >>> Brecht.
> >>> ___
> >>> Bf-committers mailing list
> >>> Bf-committers@blender.org
> >>> https://lists.blender.org/mailman/listinfo/bf-committers
> >> ___
> >> Bf-committers mailing list
> >> Bf-committers@blender.org
> >> https://lists.blender.org/mailman/listinfo/bf-committers
> >>
> > ___
> > Bf-committers mailing list
> > Bf-committers@blender.org
> > https://lists.blender.org/mailman/listinfo/bf-committers
>
> ___
> Bf-committers mailing list
> Bf-committers@blender.org
> https://lists.blender.org/mailman/listinfo/bf-committers
>
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Library updates for Blender 2.8

[Eugenio Pignataro]

Hi guys.
We will have some like install_deps.sh?

THANKS!

Untitled Document

Eugenio Pignataro
Drawing & Digital Art.
---
Site: www.oscurart.com.ar
Reel: vimeo.com/92253804
BlenderNetwork: https://www.blendernetwork.org/eugenio-pignataro
Email: i...@oscurart.com.ar
Phone: 54 15 5177 4936
Skype: info_28795
HangOut: oscurartgt...@gmail.com
On 26/07/18 13:21, Brecht Van Lommel wrote:

I think it would be great to have all these libraries updated, especially
the ones with CVEs.

* Blosc: definitely need to upgrade one to fix GCC build issues
* clew/cuew: I wonder if we even need OpenCL/CUDA support in OpenSubdiv,
maybe OpenGL is enough..
* flexbison/schroendinger/lapack: seems fine to remove
* openjpeg: don't think there is a good reason to have it in extern/
anymore, would be happy to see patch to remove it from there

I guess most of these are relatively easy with a tweak to versions.cmake,
not sure how difficult it is on Linux.


On Mon, Jul 23, 2018 at 9:54 PM Ray Molenkamp  wrote:


There's quite a few libraries we build for the various platforms
(57 by the last count) and it's not always clear who the module
owner is and who is supposed to ask for newer versions of certain
libs.

I took a quick survey of the versions we use and the latest versions
available. (based on build_files\build_environment\cmake\versions.cmake)


https://docs.google.com/spreadsheets/d/e/2PACX-1vRnu75FDmw8NvbJiH9hjrGNBvrwXU9ocWWMCWZY0ISwcfLOnL7Ep1z67Y5FpN_TaI0QRwbPR2KmrQie/pubhtml?gid=0=true

(or in case the email ruins the long link: https://tinyurl.com/y9st4fyt )

There are several libs with known CVE's, personally I would prefer
to upgrade those to the latest versions (most seem low risk upgrades)
but for everything else I really have no strong opinion.

Any module owner that wants edit rights, please poke me (email/irc) and
I'll get you an editable link.

--Ray


On 7/23/2018 11:43 AM, Brecht Van Lommel wrote:

Hi all,

It's been a while since we updated libraries, and with the upgrade to
Visual Studio 2017 this has now become easier on Windows as well. Since

the

platform maintainers have time now to do updates, let's try to get this

in

motion.

Some of the latest library versions need C++11, I also propose we require
C++11 in master. This mostly involves removing the WITH_CXX1 option and
code cleanups for STL data types compatibility.

For libraries, these are the ones I know of. Let us know if any other
library updates are needed.

* OSL, LLVM, OIIO: so we no longer need a really old LLVM version.
https://developer.blender.org/D3398
https://developer.blender.org/D2915

* OpenVDB 5.1.0: so we can read files written by other applications that
have OpenVDB 5.x.

* Python 3.7.0 (or should we wait until there is a 3.7.1 or so with
bugfixes?)

* OpenSubdiv: this will need to include a number of Sergey's bugfixes,

the

revision needed is not known (or doesn't exist) yet.

Thanks,
Brecht.
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers


___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers


___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Library updates for Blender 2.8

[Brecht Van Lommel]

I think it would be great to have all these libraries updated, especially
the ones with CVEs.

* Blosc: definitely need to upgrade one to fix GCC build issues
* clew/cuew: I wonder if we even need OpenCL/CUDA support in OpenSubdiv,
maybe OpenGL is enough..
* flexbison/schroendinger/lapack: seems fine to remove
* openjpeg: don't think there is a good reason to have it in extern/
anymore, would be happy to see patch to remove it from there

I guess most of these are relatively easy with a tweak to versions.cmake,
not sure how difficult it is on Linux.


On Mon, Jul 23, 2018 at 9:54 PM Ray Molenkamp  wrote:

> There's quite a few libraries we build for the various platforms
> (57 by the last count) and it's not always clear who the module
> owner is and who is supposed to ask for newer versions of certain
> libs.
>
> I took a quick survey of the versions we use and the latest versions
> available. (based on build_files\build_environment\cmake\versions.cmake)
>
>
> https://docs.google.com/spreadsheets/d/e/2PACX-1vRnu75FDmw8NvbJiH9hjrGNBvrwXU9ocWWMCWZY0ISwcfLOnL7Ep1z67Y5FpN_TaI0QRwbPR2KmrQie/pubhtml?gid=0=true
>
> (or in case the email ruins the long link: https://tinyurl.com/y9st4fyt )
>
> There are several libs with known CVE's, personally I would prefer
> to upgrade those to the latest versions (most seem low risk upgrades)
> but for everything else I really have no strong opinion.
>
> Any module owner that wants edit rights, please poke me (email/irc) and
> I'll get you an editable link.
>
> --Ray
>
>
> On 7/23/2018 11:43 AM, Brecht Van Lommel wrote:
> > Hi all,
> >
> > It's been a while since we updated libraries, and with the upgrade to
> > Visual Studio 2017 this has now become easier on Windows as well. Since
> the
> > platform maintainers have time now to do updates, let's try to get this
> in
> > motion.
> >
> > Some of the latest library versions need C++11, I also propose we require
> > C++11 in master. This mostly involves removing the WITH_CXX1 option and
> > code cleanups for STL data types compatibility.
> >
> > For libraries, these are the ones I know of. Let us know if any other
> > library updates are needed.
> >
> > * OSL, LLVM, OIIO: so we no longer need a really old LLVM version.
> > https://developer.blender.org/D3398
> > https://developer.blender.org/D2915
> >
> > * OpenVDB 5.1.0: so we can read files written by other applications that
> > have OpenVDB 5.x.
> >
> > * Python 3.7.0 (or should we wait until there is a 3.7.1 or so with
> > bugfixes?)
> >
> > * OpenSubdiv: this will need to include a number of Sergey's bugfixes,
> the
> > revision needed is not known (or doesn't exist) yet.
> >
> > Thanks,
> > Brecht.
> > ___
> > Bf-committers mailing list
> > Bf-committers@blender.org
> > https://lists.blender.org/mailman/listinfo/bf-committers
>
> ___
> Bf-committers mailing list
> Bf-committers@blender.org
> https://lists.blender.org/mailman/listinfo/bf-committers
>
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Library updates for Blender 2.8

[Sergey Sharybin]

Hi,

Firstly. please don't mix discussion of libraries required for Blender with
discussion about
someone-is-requesting-handy-tool-to-be-shipped-with-blender.

As for the oiiotool, guess the most use of it is to generate .tx. In this
case Blender can do it using library API, no need to call an external
process. If that is for another type of integration purpose -- i'd say such
tools do not belong to Blender package. There are far too many handy tools
which lots of people will want have distributed. That would easily bump
package size to over 10 gig.

If that is just to give random folks builds -- i am even more against it.
We are not a building service for that library, and i don't want even get
close to opening discussions like "can you update 
because we definitely need a newer version for our purpose (which, btw, has
nothing to do with Blender)".

In any case, suggest moving this discussion to a separate topic.

On Tue, Jul 24, 2018 at 1:46 PM Ray Molenkamp  wrote:

> Currently we're only shipping idiff since the unit tests need it, we could
> add the other tools
> however since we build for blender they are all statically linked, so just
> oiiotool would be
> 12 megs, while the whole set of binaries would be 45. not sure we want to
> add this much
> dead weight to the libs?
>
> --Ray
>
> On 7/24/2018 12:36 AM, Stefan Werner wrote:
> > While not directly applicable to Blender, would it be any trouble to
> include oiiotool.exe in the Windows binaries? There was just someone asking
> for binaries on the oiio mailing list:
> >
> http://lists.openimageio.org/pipermail/oiio-dev-openimageio.org/2018-July/001254.html
> <
> http://lists.openimageio.org/pipermail/oiio-dev-openimageio.org/2018-July/001254.html
> >
> >
> > -Stefan
> >
> >> On 23. Jul 2018, at 21:53, Ray Molenkamp  wrote:
> >>
> >> There's quite a few libraries we build for the various platforms
> >> (57 by the last count) and it's not always clear who the module
> >> owner is and who is supposed to ask for newer versions of certain
> >> libs.
> >>
> >> I took a quick survey of the versions we use and the latest versions
> >> available. (based on build_files\build_environment\cmake\versions.cmake)
> >>
> >>
> https://docs.google.com/spreadsheets/d/e/2PACX-1vRnu75FDmw8NvbJiH9hjrGNBvrwXU9ocWWMCWZY0ISwcfLOnL7Ep1z67Y5FpN_TaI0QRwbPR2KmrQie/pubhtml?gid=0=true
> >>
> >> (or in case the email ruins the long link: https://tinyurl.com/y9st4fyt
> )
> >>
> >> There are several libs with known CVE's, personally I would prefer
> >> to upgrade those to the latest versions (most seem low risk upgrades)
> >> but for everything else I really have no strong opinion.
> >>
> >> Any module owner that wants edit rights, please poke me (email/irc) and
> >> I'll get you an editable link.
> >>
> >> --Ray
> >>
> >>
> >> On 7/23/2018 11:43 AM, Brecht Van Lommel wrote:
> >>> Hi all,
> >>>
> >>> It's been a while since we updated libraries, and with the upgrade to
> >>> Visual Studio 2017 this has now become easier on Windows as well.
> Since the
> >>> platform maintainers have time now to do updates, let's try to get
> this in
> >>> motion.
> >>>
> >>> Some of the latest library versions need C++11, I also propose we
> require
> >>> C++11 in master. This mostly involves removing the WITH_CXX1 option and
> >>> code cleanups for STL data types compatibility.
> >>>
> >>> For libraries, these are the ones I know of. Let us know if any other
> >>> library updates are needed.
> >>>
> >>> * OSL, LLVM, OIIO: so we no longer need a really old LLVM version.
> >>> https://developer.blender.org/D3398
> >>> https://developer.blender.org/D2915
> >>>
> >>> * OpenVDB 5.1.0: so we can read files written by other applications
> that
> >>> have OpenVDB 5.x.
> >>>
> >>> * Python 3.7.0 (or should we wait until there is a 3.7.1 or so with
> >>> bugfixes?)
> >>>
> >>> * OpenSubdiv: this will need to include a number of Sergey's bugfixes,
> the
> >>> revision needed is not known (or doesn't exist) yet.
> >>>
> >>> Thanks,
> >>> Brecht.
> >>> ___
> >>> Bf-committers mailing list
> >>> Bf-committers@blender.org
> >>> https://lists.blender.org/mailman/listinfo/bf-committers
> >> ___
> >> Bf-committers mailing list
> >> Bf-committers@blender.org
> >> https://lists.blender.org/mailman/listinfo/bf-committers
> > ___
> > Bf-committers mailing list
> > Bf-committers@blender.org
> > https://lists.blender.org/mailman/listinfo/bf-committers
>
> ___
> Bf-committers mailing list
> Bf-committers@blender.org
> https://lists.blender.org/mailman/listinfo/bf-committers
>


-- 
With best regards, Sergey Sharybin
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Library updates for Blender 2.8

[Ray Molenkamp]

Currently we're only shipping idiff since the unit tests need it, we could add 
the other tools
however since we build for blender they are all statically linked, so just 
oiiotool would be
12 megs, while the whole set of binaries would be 45. not sure we want to add 
this much
dead weight to the libs?

--Ray

On 7/24/2018 12:36 AM, Stefan Werner wrote:
> While not directly applicable to Blender, would it be any trouble to include 
> oiiotool.exe in the Windows binaries? There was just someone asking for 
> binaries on the oiio mailing list:
> http://lists.openimageio.org/pipermail/oiio-dev-openimageio.org/2018-July/001254.html
>  
> 
>
> -Stefan
>
>> On 23. Jul 2018, at 21:53, Ray Molenkamp  wrote:
>>
>> There's quite a few libraries we build for the various platforms
>> (57 by the last count) and it's not always clear who the module
>> owner is and who is supposed to ask for newer versions of certain
>> libs. 
>>
>> I took a quick survey of the versions we use and the latest versions
>> available. (based on build_files\build_environment\cmake\versions.cmake)
>>
>> https://docs.google.com/spreadsheets/d/e/2PACX-1vRnu75FDmw8NvbJiH9hjrGNBvrwXU9ocWWMCWZY0ISwcfLOnL7Ep1z67Y5FpN_TaI0QRwbPR2KmrQie/pubhtml?gid=0=true
>>
>> (or in case the email ruins the long link: https://tinyurl.com/y9st4fyt )
>>
>> There are several libs with known CVE's, personally I would prefer
>> to upgrade those to the latest versions (most seem low risk upgrades)
>> but for everything else I really have no strong opinion.
>>
>> Any module owner that wants edit rights, please poke me (email/irc) and
>> I'll get you an editable link.
>>
>> --Ray
>>
>>
>> On 7/23/2018 11:43 AM, Brecht Van Lommel wrote:
>>> Hi all,
>>>
>>> It's been a while since we updated libraries, and with the upgrade to
>>> Visual Studio 2017 this has now become easier on Windows as well. Since the
>>> platform maintainers have time now to do updates, let's try to get this in
>>> motion.
>>>
>>> Some of the latest library versions need C++11, I also propose we require
>>> C++11 in master. This mostly involves removing the WITH_CXX1 option and
>>> code cleanups for STL data types compatibility.
>>>
>>> For libraries, these are the ones I know of. Let us know if any other
>>> library updates are needed.
>>>
>>> * OSL, LLVM, OIIO: so we no longer need a really old LLVM version.
>>> https://developer.blender.org/D3398
>>> https://developer.blender.org/D2915
>>>
>>> * OpenVDB 5.1.0: so we can read files written by other applications that
>>> have OpenVDB 5.x.
>>>
>>> * Python 3.7.0 (or should we wait until there is a 3.7.1 or so with
>>> bugfixes?)
>>>
>>> * OpenSubdiv: this will need to include a number of Sergey's bugfixes, the
>>> revision needed is not known (or doesn't exist) yet.
>>>
>>> Thanks,
>>> Brecht.
>>> ___
>>> Bf-committers mailing list
>>> Bf-committers@blender.org
>>> https://lists.blender.org/mailman/listinfo/bf-committers
>> ___
>> Bf-committers mailing list
>> Bf-committers@blender.org
>> https://lists.blender.org/mailman/listinfo/bf-committers
> ___
> Bf-committers mailing list
> Bf-committers@blender.org
> https://lists.blender.org/mailman/listinfo/bf-committers

___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Library updates for Blender 2.8

[Stefan Werner]

While not directly applicable to Blender, would it be any trouble to include 
oiiotool.exe in the Windows binaries? There was just someone asking for 
binaries on the oiio mailing list:
http://lists.openimageio.org/pipermail/oiio-dev-openimageio.org/2018-July/001254.html
 


-Stefan

> On 23. Jul 2018, at 21:53, Ray Molenkamp  wrote:
> 
> There's quite a few libraries we build for the various platforms
> (57 by the last count) and it's not always clear who the module
> owner is and who is supposed to ask for newer versions of certain
> libs. 
> 
> I took a quick survey of the versions we use and the latest versions
> available. (based on build_files\build_environment\cmake\versions.cmake)
> 
> https://docs.google.com/spreadsheets/d/e/2PACX-1vRnu75FDmw8NvbJiH9hjrGNBvrwXU9ocWWMCWZY0ISwcfLOnL7Ep1z67Y5FpN_TaI0QRwbPR2KmrQie/pubhtml?gid=0=true
> 
> (or in case the email ruins the long link: https://tinyurl.com/y9st4fyt )
> 
> There are several libs with known CVE's, personally I would prefer
> to upgrade those to the latest versions (most seem low risk upgrades)
> but for everything else I really have no strong opinion.
> 
> Any module owner that wants edit rights, please poke me (email/irc) and
> I'll get you an editable link.
> 
> --Ray
> 
> 
> On 7/23/2018 11:43 AM, Brecht Van Lommel wrote:
>> Hi all,
>> 
>> It's been a while since we updated libraries, and with the upgrade to
>> Visual Studio 2017 this has now become easier on Windows as well. Since the
>> platform maintainers have time now to do updates, let's try to get this in
>> motion.
>> 
>> Some of the latest library versions need C++11, I also propose we require
>> C++11 in master. This mostly involves removing the WITH_CXX1 option and
>> code cleanups for STL data types compatibility.
>> 
>> For libraries, these are the ones I know of. Let us know if any other
>> library updates are needed.
>> 
>> * OSL, LLVM, OIIO: so we no longer need a really old LLVM version.
>> https://developer.blender.org/D3398
>> https://developer.blender.org/D2915
>> 
>> * OpenVDB 5.1.0: so we can read files written by other applications that
>> have OpenVDB 5.x.
>> 
>> * Python 3.7.0 (or should we wait until there is a 3.7.1 or so with
>> bugfixes?)
>> 
>> * OpenSubdiv: this will need to include a number of Sergey's bugfixes, the
>> revision needed is not known (or doesn't exist) yet.
>> 
>> Thanks,
>> Brecht.
>> ___
>> Bf-committers mailing list
>> Bf-committers@blender.org
>> https://lists.blender.org/mailman/listinfo/bf-committers
> 
> ___
> Bf-committers mailing list
> Bf-committers@blender.org
> https://lists.blender.org/mailman/listinfo/bf-committers

___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Library updates for Blender 2.8

[Ray Molenkamp]

There's quite a few libraries we build for the various platforms
(57 by the last count) and it's not always clear who the module
owner is and who is supposed to ask for newer versions of certain
libs. 

I took a quick survey of the versions we use and the latest versions
available. (based on build_files\build_environment\cmake\versions.cmake)

https://docs.google.com/spreadsheets/d/e/2PACX-1vRnu75FDmw8NvbJiH9hjrGNBvrwXU9ocWWMCWZY0ISwcfLOnL7Ep1z67Y5FpN_TaI0QRwbPR2KmrQie/pubhtml?gid=0=true

(or in case the email ruins the long link: https://tinyurl.com/y9st4fyt )

There are several libs with known CVE's, personally I would prefer
to upgrade those to the latest versions (most seem low risk upgrades)
but for everything else I really have no strong opinion.

Any module owner that wants edit rights, please poke me (email/irc) and
I'll get you an editable link.

--Ray


On 7/23/2018 11:43 AM, Brecht Van Lommel wrote:
> Hi all,
>
> It's been a while since we updated libraries, and with the upgrade to
> Visual Studio 2017 this has now become easier on Windows as well. Since the
> platform maintainers have time now to do updates, let's try to get this in
> motion.
>
> Some of the latest library versions need C++11, I also propose we require
> C++11 in master. This mostly involves removing the WITH_CXX1 option and
> code cleanups for STL data types compatibility.
>
> For libraries, these are the ones I know of. Let us know if any other
> library updates are needed.
>
> * OSL, LLVM, OIIO: so we no longer need a really old LLVM version.
> https://developer.blender.org/D3398
> https://developer.blender.org/D2915
>
> * OpenVDB 5.1.0: so we can read files written by other applications that
> have OpenVDB 5.x.
>
> * Python 3.7.0 (or should we wait until there is a 3.7.1 or so with
> bugfixes?)
>
> * OpenSubdiv: this will need to include a number of Sergey's bugfixes, the
> revision needed is not known (or doesn't exist) yet.
>
> Thanks,
> Brecht.
> ___
> Bf-committers mailing list
> Bf-committers@blender.org
> https://lists.blender.org/mailman/listinfo/bf-committers

___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Library updates for Blender 2.8

[Brecht Van Lommel]

Hi all,

It's been a while since we updated libraries, and with the upgrade to
Visual Studio 2017 this has now become easier on Windows as well. Since the
platform maintainers have time now to do updates, let's try to get this in
motion.

Some of the latest library versions need C++11, I also propose we require
C++11 in master. This mostly involves removing the WITH_CXX1 option and
code cleanups for STL data types compatibility.

For libraries, these are the ones I know of. Let us know if any other
library updates are needed.

* OSL, LLVM, OIIO: so we no longer need a really old LLVM version.
https://developer.blender.org/D3398
https://developer.blender.org/D2915

* OpenVDB 5.1.0: so we can read files written by other applications that
have OpenVDB 5.x.

* Python 3.7.0 (or should we wait until there is a 3.7.1 or so with
bugfixes?)

* OpenSubdiv: this will need to include a number of Sergey's bugfixes, the
revision needed is not known (or doesn't exist) yet.

Thanks,
Brecht.
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers