Our integration of OCIO with oiiotool was quite rough - it was just a
place-holder until the official version was done.
In terms of my initial question, all of the OIIO installation docs imply
that I should only ever be calling 'make' directly, and not 'cmake' - it
seems like OCIO_PATH is some
Yah, I'll try to make this all clearer before we push to master. (it's not
quite ready yet, I'm still working on addressing lg's comments).
USE_OCIO=1 is the default, and shouldnt be necessary.
OCIO_PATH should be a directory that has (at least) 2 subdirs, 'include'
and 'lib'. If for some reaso
On Sun, Dec 11, 2011 at 10:49 AM, Hugh Macdonald
wrote:
> Hi,
>
> I'm sure I'm missing something incredibly obvious here, but I seem to be
> unable to compile OIIO with OCIO support.
>
> I've got Jeremy's ocio branch of OIIO, and running 'make help' mentions:
>
> make USE_OCIO=1 ... Spec
Hi,
I'm sure I'm missing something incredibly obvious here, but I seem to be unable
to compile OIIO with OCIO support.
I've got Jeremy's ocio branch of OIIO, and running 'make help' mentions:
make USE_OCIO=1 ... Specify whether to build with OpenColorIO support
(Incidentally, this li
