Yes, though I dont really know what precisely it means to package OCIO. Does it basically involve making a higher-level config file that includes the build commands? Would the process be similar for getting OCIO / OIIO support on macports / etc?
I've talked with Peter Linnell previously about packaging up OCIO (he is involved with Debian), and he mentioned that there would have to be a few minor build modifications. (The one I remember being that OCIO ships with some internal dependencies, and he recommends configuring the build process to use the system installed ones if they're already installed). -- Jeremy On Wed, Nov 16, 2011 at 8:52 AM, Richard Shaw <hobbes1...@gmail.com> wrote: > On Wed, Nov 16, 2011 at 10:49 AM, Jeremy Selan <jeremy.se...@gmail.com> wrote: >> 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? > > Mostly :) So basically I still need to package OCIO? > > 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
