Also worth mentioning... Although Toshio (from Fedora devel list) thought it was strange for the python library to serve a dual purpose, he agreed that the most appropriate action was to put the

<malcolmh...@...> wrote: Usually it's the packagers job to decide on how to break up the packages as the guidelines differ somewhat between distros, but documented suggestions are very

Off list Jeremy, Colin and myself were chatting about this when talking about the windows build. .... We need to have a consensus on how the project will be split up into packages (ie different sets

Placeholder for continued discussion from: https://github.com/imageworks/OpenColorIO/pull/183

https://github.com/imageworks/OpenColorIO/pull/183

I did start to play around with using cpack for this to create the relevant installers (rpm, deb, tar, exe etc..) I should have some free time to get around to cleaning this up and committing

Awesome! And now that I have a Windows machine available, once we get the process sorted out I'm happy to post pre-built installers (mac, windows, linux?) for each dot release. --

Hi there - If no one else beats me to it I'll try to put together a fork of the project that should work out of the box on Windows together in the next week or two along with some pre-built binaries

Hi guys! Just want to second that some more windows-friendly documentation/ precompiles would really be appreciated. Not very experienced in this, but I`m trying to compile thru cygwin and I am almost

Yes, 1.0.1. 1.) I saw errors that patch is not a recognized program. (As Colin mentioned I downloaded cygwin and put it on the path). 2.) Finding the OCIO_USE_BOOST_PTR Cmake setting cleared out

This works like a charm now! Thanks, Jordan

As far as I know, Windows should be building right out of the box. I presume you're using 1.0.X, correct? Colin's email you cite below is from May. In August, the Foundry committed 2 changes should

Hi all, I'm resurrecting this thread to see about the current state of building OCIO for Windows. I was able to get Cmake to generate a VS 2008 solution, but it isn't compiling. Colin's list of fixes

I've just rolled this patch into master. Jordan / dbr, please let me know if you encounter any further issues on Lion. -- Jeremy

Marie, I am VERY late to the party but a linear spaced 32 or 64 segment lut from aces to a ssrt/odt will be insufficent. You can create a ACES ADX-> rrt/odt 32 or 64 lut and get acceptable results.

A fix for this was just committed to master: https://github.com/imageworks/OpenColorIO/pull/177 Please let me know if you have any other compatibility issues with 3dl export. -- Jeremy

https://github.com/imageworks/OpenColorIO/pull/178 Added options for specifying simple color corrections (such as saturation, offsets, etc) in addition to normal lut commands. Also allow for

https://github.com/imageworks/OpenColorIO/pull/177 Previously, flame and lustre 3dl export was hard-coded to size 17 shaper luts, even when the cubelut was a different size (33x33x33 for lustre, for

Version 1.0.1 (Oct 31 2011): * Luts with incorrect extensions are properly loaded * ocio2icc / ociobakelut get --lut option (no longer requires ocio config) * DisplayTransform looks do not

This feels like a bug (not having the shaper lut obey the specified size). If I remember correctly (the last time I tested at least) flame only supportex size 17 luts, so even if we make the fix it