[Bf-committers] Library updates for Blender 2.8

Sergey Sharybin sergey.vfx at gmail.com
Tue Jul 24 16:53:19 CEST 2018


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 <whatever-library>
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 <ray at lazydodo.com> 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 <ray at lazydodo.com> 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&single=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 at blender.org
> >>> https://lists.blender.org/mailman/listinfo/bf-committers
> >> _______________________________________________
> >> Bf-committers mailing list
> >> Bf-committers at blender.org
> >> https://lists.blender.org/mailman/listinfo/bf-committers
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at blender.org
> > https://lists.blender.org/mailman/listinfo/bf-committers
>
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> https://lists.blender.org/mailman/listinfo/bf-committers
>


-- 
With best regards, Sergey Sharybin


More information about the Bf-committers mailing list