I can see how it's confusing.  The version numbers and release schedules of the 
two packages are independent.

Officially, OIIO 1.1.x is the approved stable release for production use 
(stable, tested, controlled releases, with APIs will not change in an 
incompatible way), and the master trunk is in-progress work on what will 
eventually be OIIO 1.2 (subject to constant change, including compatibility 
breaks).

For OSL, 1.2 is the stable release for production use, and master is the 
work-in-progress 1.3 (though it tends to be extremely solid, since at Sony 
Imageworks we build for our productions straight out of master, so if anything 
breaks, I'm on the hook to have it fixed IMMEDIATELY).

I believe that OSL 1.2 and master both assume that they are linked against OIIO 
>= 1.1.  I make no promises about any other combinations of older OSL or OIIO 
branches.  If any major OSL user cared about a particular old version of OIIO, 
I'd work hard to ensure compatibility, but so far, nobody has complained that 
my strategy is inadequate.

OIIO 0.10.x is very old. I'm pretty sure that the (commercial) SolidAngle 
Arnold product is the only user still on an OIIO version this old (I believe 
they are just waiting for the right spot in their release schedule to jump 
forward a few OIIO releases). Since they haven't (to the best of my knowledge) 
attempted to incorporate OSL into their version of Arnold, OSL compatibility 
with this ancient OIIO has never been an issue.

Can you clarify... did you check out OIIO 0.10.x just because you used Arnold 
to guess a version for you to start with? Or do you have an actual requirement 
to be link-compatible with Arnold?

If you MUST be link-compatible with Arnold (say, you are using OSL in a plug-in 
for it), then I'm happy to back-port "round_to_multiple" (and, within reason, 
other things that don't appear to jeopardize stability or break the APIs) to 
OIIO 0.10.  You'd need to wait for (or request) those changes to be picked up 
by SolidAngle and distribute a new build that incorporates it; I certainly 
don't control that part of the process.

Does any of this actually answer your question?

        -- lg


On Apr 1, 2013, at 8:31 PM, [email protected] wrote:

> Hi Larry,
> 
> Would you like to tell me the relationship about version number between OSL 
> and OIIO ? Since Arnold-4.0.12.0-windows is using 0.10.15.0, so that I 
> prepared the 0.10.16 from github, and when I was trying to compile OSL 
> remotes/origin/RB-1.1, it refered the non-existed function 
> OIIO::round_to_multiple, so is there any way to fix this ? Thanks !
> _______________________________________________
> Oiio-dev mailing list
> [email protected]
> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org

--
Larry Gritz
[email protected]


_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org

Reply via email to