Hi, It might have to wait a few weeks, I'm in Hong Kong right now and I'm going to be MIA in asia for a bit. But yes a chat would be good when we are both free. They are a common mechanism for setting

+1 it should be pretty easy to add boost back as a dependency if we need to. I have seen a lot of projects copy the shared_ptr so it seems fairly common practice. .malcolm

LGTM

+1 it should be pretty easy to add boost back as a dependency if we need to. I have seen a lot of projects copy the shared_ptr so it seems fairly common practice. .malcolm

LGTM

I've added a nuke python script to src/testbed that lets you export specified nuke color spaces into an OCIO profile. It also is a good example of using the python API to create an OCIO

A new profile, 'nuke-default' has been added to the 0.7.1 config bundle. http://sites.google.com/site/opencolorio/profiles This profile emulates the 'out of the box' color processing luts that come

Hey Jeremy, The build completes successfully commenting out that line. If things are as Est mentioned, then I think this is a good idea. It would be preferable to use the distribution's supplied

I had the same problem. It happens when you link to the dynamic version of boost's test libraries. You need to build / install boost test as static libraries and point CMake to them. Est.

shared_ptr is part of C++0x (in TR1, I think). So another approach is to rig it so that sufficiently new compilers don't need the boost dependency, and only the old compilers will need to pull it in

Would anyone be against us copying the shared_ptr implementation internally into OCIO? That would let us make the OCIO boost dependency optional, which would let it compile on a plain-vanilla

Trivial addition, exposed ROLE_DEFAULT to python. commit 82dd5a4666f7c5456361e9ec7d78107742e5b427 -- Jeremy

I haven't seen that issue before, but it looks like it's related to the testing framework (which relies on boost). I'll try to get an Ubuntu machine up in the next few days for testing. But... in

We're starting to get some actual OCIO users, so it's time to start a new mailing list: http://groups.google.com/group/ocio-users This will focus on issues related to color profile development,

Hey everyone, I've encountered a linker issue on Ubuntu 10.10 with ocio-0.7.0. I was wondering if anyone could shed some light on whats going on? Linking CXX executable

Color profiles suitable for OCIO 0.7 have been posted, along with basic documentation. See https://sites.google.com/site/opencolorio/profiles for additional information. Note 1: Thanks to Joseph

Rod, This is my partial follow-up to Jeremy's response. A reference space is a useful concept and Imageworks will use them for AMPAS IIF implementation. The colorimetry will match the

There's a lot of good ideas here, it's taken me a bit of time to think through the implications. I'm going to be out of town for the remainder of the week, perhaps we could try an internet call early

Excellent, thanks. <malcolmh...@...> wrote:

Sorry I never noticed that section in the main CMakelists file, it all looks good. "Jeremy Selan" <jeremy...@...> wrote: -- Sent from my phone.