CMake is looking for the normal boost installation, and it can't find it. Have you installed it in a non-standard location? You can tell CMake about where boost is with: -D BOOST_INCLUDEDIR -D BOOST_L

I keep getting this error: OCIO_USE_BOOST_PTR is specified, but a boost installation could not be found. I just installed a full boost Pro 1.47 installation - so what exactly is cmake looking for? I d

I'll hold off on commenting on the first issue for the moment, but the 2nd issue (not preserving incoming CMAKE_CXX_FLAGS) is clearly an oversight. I'll check in a fix today. -- Jeremy

Hi, When building the apps that come with OpenColorIO I hit the following errors (under gcc): [EE] /user_data/ARCHIVE/imageworks-OpenColorIO-de86248/src/apps/ocioconvert/main.cpp:37: error: 'OIIO_NAME

Hi, I've hit upon a couple of issues when trying to build the core OpenColorIO lib. a) The following error occurs: /usr/bin/ld: CMakeFiles/OpenColorIO.dir/Baker.cpp.o: relocation R_X86_64_PC32 against

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

Hello ! I was considering porting some OpenColorIO Nuke Nodes in OFX to use them in TuttleOFX (among others). It reminds me that this subject was already discussed here (see below). How are things goi

I just noticed when running rpmlint on my installation of OpenImageIO that PyOpenImageIO can't find a lot of python symbols. I looked in the cmake config for pyglue and noticed that the python librari

Version 1.0.2 (Nov 30 2011): * 3D lut processing (cpu) is resiliant to nans * Nuke OCIOFileTransform gains Reload buttons * Installation on multi-lib *nix systems improved * Installation handling of s

https://github.com/imageworks/OpenColorIO/pull/190 Previously, the software implementation of Lut3DOp would stop processing the scanline when a nan was encountered (due to a bad if/else condition). Th

Hi everyone, Recently I've tried using the ociotoicc utility with a lut on the command line. When I try to load the icc file into photoshop, I receive: "Could not load the RGB working space because th

https://github.com/imageworks/OpenColorIO/pull/187 This is mostly about the JNI Java interface, you need to run cmake with (-D OCIO_BUILD_JNIGLUE=TRUE) for the binding to be built. Their is no install

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

Hi All, Wish I could have figured this out myself (I had no issues building pre-1.0 source on my MacBook Air Snow Leopard laptop, but I'm having issues building the latest 1.0 source now. I'm not doin

Marie, Thanks for catching this! The currently shipping IIF configuration is based on an older specification (I forget the exact version, but it's around 8 months old), so my hope is the versions will

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 specifica

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 e

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 apply to 'd

https://github.com/imageworks/OpenColorIO/pull/174 DisplayTransform looks are no longer automatically applied to 'data' ('data' being normals, pts, etc). By design, colorspaces tagged as data do not h

Adds --lut option, which lets you create a baked output lut, even in the absence of an input configuration. Example: ociobakelut --lut filmlut.3dl --lut calibration.3dl --format flame lg_to_srgb.3dl h