[Bf-committers] Library updates for Blender 2.8
ray at lazydodo.com
Tue Jul 24 13:46:17 CEST 2018
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?
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>
>> 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
>> I took a quick survey of the versions we use and the latest versions
>> available. (based on build_files\build_environment\cmake\versions.cmake)
>> (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.
>> 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
>>> 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.
>>> * 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
>>> * OpenSubdiv: this will need to include a number of Sergey's bugfixes, the
>>> revision needed is not known (or doesn't exist) yet.
>>> Bf-committers mailing list
>>> Bf-committers at blender.org
>> Bf-committers mailing list
>> Bf-committers at blender.org
> Bf-committers mailing list
> Bf-committers at blender.org
More information about the Bf-committers