OCIO 1.0.7 released


Jeremy Selan <jeremy...@...>
 

This release is a duesy.

OCIO 1.0.7 is ABI and source compatible with all 1.X versions (of
course), but has a lot of features / fixes:

Version 1.0.7 (April 17 2012):
* IRIDAS .look support
* ociolutimage utility added (handles image <-> 3dlut)
* CMake build allows optional reliance on system libraries
* CMake layout changes for python and nuke installs
* Bumped internals to yaml 0.3.0, pystring 1.1.2
* Optimized internal handling of Matrix / Exponent Ops
* Added INTERP_BEST interpolation option
* Python config.clearLooks() added
* Python docs revamp
* Nuke config-dependent knob values now baked into .nk scripts
* Nuke OCIOLookTransform gets reload button
* Nuke nodes get updated help text

For those who have automated installation 'recipes', those will need
to be double-checked due to the installation updates.

Download from opencolorio.org/downloads.html

Enjoy!

-- Jeremy


Richard Shaw <hobbe...@...>
 

On Tue, Apr 17, 2012 at 7:29 PM, Jeremy Selan <jeremy...@...> wrote:
This release is a duesy.

OCIO 1.0.7 is ABI and source compatible with all 1.X versions (of
course), but has a lot of features / fixes:
Once quick note. It looks like we're installing real libraries in the
python site-packages directory. In looking at what I already have in
there, none of them have sonames/soversions but the project now builds
them that way. I'm thinking we should probably disable sonames for the
python libraries.

Richard


Jeremy Selan <jeremy...@...>
 

Thanks for catching that. I'll try to get the fix validated and we'll
push out a 1.0.7-1 today.

-- Jeremy

On Wed, Apr 18, 2012 at 8:10 AM, Richard Shaw <hobbe...@...> wrote:
On Tue, Apr 17, 2012 at 7:29 PM, Jeremy Selan <jeremy...@...> wrote:
This release is a duesy.

OCIO 1.0.7 is ABI and source compatible with all 1.X versions (of
course), but has a lot of features / fixes:
Once quick note. It looks like we're installing real libraries in the
python site-packages directory. In looking at what I already have in
there, none of them have sonames/soversions but the project now builds
them that way. I'm thinking we should probably disable sonames for the
python libraries.

Richard


Richard Shaw <hobbe...@...>
 

On Wed, Apr 18, 2012 at 1:22 PM, Jeremy Selan <jeremy...@...> wrote:
Thanks for catching that.  I'll try to get the fix validated and we'll
push out a 1.0.7-1 today.
I went ahead an did a pull request. Got to keep my github-fu strong(er) :)

Also a quick fix on the documentation. Some non-git related hidden
files were making their way into the installed docs.

Richard