I wouldnt call it a merge, OCIO and OIIO will still be 2 separate projects. But our intent is to add OCIO functionality into OIIO as an optional build-time option. So I guess you'd say the OIIO will have OCIO as an optional dependency.
(The public ABI to OIIO will be identical in both cases though). Makes sense? -- Jeremy On Wed, Nov 16, 2011 at 8:46 AM, Richard Shaw <hobbes1...@gmail.com> wrote: > On Wed, Nov 16, 2011 at 10:31 AM, Jeremy Selan <jeremy.se...@gmail.com> wrote: >> Cool! Have you let the field3d guys know as well? >> http://groups.google.com/group/field3d-dev >> >> I'm sure they'd be interested. > > Just sent an email to their group, thanks for the link. > > >> Any interest in tackling OpenColorIO as well at some point? ;) > > Well if I understand correctly, ocio is going to be merged into oiio > fairly soon anyway, right? > > Thanks, > Richard > _______________________________________________ > Oiio-dev mailing list > Oiio-dev@lists.openimageio.org > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org > _______________________________________________ Oiio-dev mailing list Oiio-dev@lists.openimageio.org http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
