Great! how can you remove OIIO/OCIO from Mari without breaking functionality? We are planning on using OCIO in Mari at some point.
Dave. Dave Lajoie R&D Director | Directeur R&D [image: Digital-District] <http://www.digital-district.fr> 5605 Avenue de Gaspé, Suite 408 | Montréal, QC H2T 2A4 Tel (514) 360-3253 ext. 130 On Tue, Sep 16, 2014 at 12:50 PM, Larry Gritz <[email protected]> wrote: > Is this resolved, then? Is there anything I can do on the OIIO side that > would make it better for you? > > -- lg > > > On Sep 16, 2014, at 9:38 AM, Ashley Retallack <[email protected]> > wrote: > > We ended up removing the OpenColorIO libraries from mari as they were > confusing things and instead using our shared libraries. > > On 16 September 2014 17:13, Dave Lajoie <[email protected]> > wrote: > >> Hello Guys, I don't know if someone has been experiencing the same >> problem. >> >> Basically we have compiled OpenImageIO ( 1.4 and 1.5 master ) along with >> Python Bindings, but whenever the python module is being imported in Mari >> 2.6v2 (Linux CentOS6.5) >> >> We get this error: >> >> Built on 2014-05-30 at 10:14, using Python 2.6.5. >> Welcome to Mari 2.6v2! Type help() to get started. >> >>> import OpenImageIO >> Traceback (most recent call last): >> File "<string>", line 1, in <module> >> >> ImportError: /path/path/path/1.4/lib/libOpenImageIO.so.1.4: undefined >> symbol: _ZTIN11OpenColorIO2v19ExceptionE >> >> >> If I remember correctly, we compiled oiio and components with OCIO >> dependencies, and also we have statically link external libraries, as much >> as possible. >> >> How can I resolve this symbol issue? >> Tx >> Dave. >> > > -- > Larry Gritz > [email protected] > > > > > _______________________________________________ > Oiio-dev mailing list > [email protected] > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org > >
_______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
