I truly don't understand this report. There are only 6 commits between 1.0.11
and 1.0.12, and none of them involve the files in which gettexels() or
texture3d() are either declared or used.
Are you able to get any more specific detail about what it thinks changed that
would break ABI compatibility? I'm not seeing anything in the code that would
do this between these two releases.
-- lg
On Jul 3, 2013, at 12:15 PM, Richard Shaw wrote:
> I am working on updating OIIO on Fedora and with the upgrade policy as it is,
> it is recommended I don't perform major upgrades within a release so while
> Fedora 19 and Rawhide are on the 1.1 branch, Fedora 17 and 18 are on the 1.0
> branch.
>
> I did my usual abi-compliance-checker on 1.0.11 vs. 1.0.12 and it showed some
> possible issues:
>
> https://dl.dropboxusercontent.com/u/34775202/compat_reports/OpenImageIO/1.0.11_to_1.0.12/compat_report.html
>
> I do have the ability to rebuild blender if required (the only direct
> dependency in Fedora) but I prefer not to if I can help it. If I have to
> rebuild I might as well update all the releases to 1.1.x...
>
> On a side note, the 1.1.11 to 1.1.13 abi check came out good...
>
> https://dl.dropboxusercontent.com/u/34775202/compat_reports/OpenImageIO/1.1.11_to_1.1.13/compat_report.html
>
> Thanks,
> Richard
>
--
Larry Gritz
[email protected]
_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
