On Wed, Nov 16, 2011 at 11:03 AM, Jeremy Selan <jeremy.se...@gmail.com> wrote: > 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 would guess that's equivalent. When I say package I mean compile and put the resultant binaries and libraries into a RPM package that can be easily installed by an end user with the native Fedora tools. > 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). I just started the build process, we'll see what I run in to. I notice that it has optional dependencies for two proprietary technologies, Nuke and TrueLight that it will obviously not be built with. Richard _______________________________________________ Oiio-dev mailing list Oiio-dev@lists.openimageio.org http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
