Maybe in the short term just moving them into another folder exampleapps might do?
On 06/12/2011, at 7:44 PM, Jeremy Selan 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). > > -- Jeremy > > > On Tue, Dec 6, 2011 at 11:08 AM, Richard Shaw <hobbes1...@gmail.com> wrote: > I wasn't sure how to phrase it in the subject, but OCIO also links > against OIIO, right? > > So does that mean to get both to know about each other that one of the > two will have to be built twice? > > What I mean by that is: > - First you build OCIO or OIIO without the other. > - Then you build the other that can now link against the first. > - Now you have to build the first again so it can link against the second. > > Would you call this cross-linking? :) > > 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
_______________________________________________ Oiio-dev mailing list Oiio-dev@lists.openimageio.org http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
