On Tue, Dec 6, 2011 at 1:44 PM, Jeremy Selan <jeremy.se...@gmail.com> wrote: > The core OCIO library does *not* link to OIIO, to avoid cyclical > dependencies, as you suggest. > > What you're seeing is that OCIO comes with two example apps, ociodisplay + > ocioconvert, which do link to OIIO. But in my opinion these binaries are > 'toy' apps, and only serve as code examples. I'm happy to move these two > chunks of code either out of the makefile, or into OIIO's codebase. (OCIO > does ship with other 'real' workhorse apps, ocioconvert, ocio2icc, > ociobakelut, but these do not link to OIIO).
Either one works for me, it was just an observation. I haven't tried it yet, but I assume that the build for OCIO skips the example programs if the OIIO headers are not available? Thanks, Richard _______________________________________________ Oiio-dev mailing list Oiio-dev@lists.openimageio.org http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
