Ok, I tested some more and learned a few things. I don't think OIIO needs
to be modified after all.
On my Mac, homebrew has installed OpenEXR/Imath 3.x with their
corresponding cmake configs in /usr/local/{lib,include}. This is because I
have (of all things) ffmpeg installed with homebrew, and right now it
appears ffmpeg's homebrew package dependencies include openexr indirectly:
ffmpeg -> aom -> jpeg-xl -> openexr [1].
The USD build script is downloading and building OpenEXR 2.x to a custom
path. But when the USD build script tries to build OIIO, I see where OIIO's
FindOpenEXR.cmake is picking up the version of Imath 3.x in /usr/local.
I'm assuming that's happening here [2] with "find_package(Imath CONFIG)".
So in my new test, rather than mess around with "-isystem" I'm
passing "-DCMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH=False" into cmake to
deter it from finding those packages in system paths [3]. That flag didn't
help my build of OIIO 2.1.16.0 / OpenEXR 2.3.0, but is working with OIIO
v2.3.10.1 / OpenEXR 2.5.7. Since I prefer the newer library versions
anyway, I'm inclined to just test the build I've got and move forward.
Neil
[1] brew deps ffmpeg; brew uses openexr --installed
[2]
https://github.com/OpenImageIO/oiio/blob/master/src/cmake/modules/FindOpenEXR.cmake#L38-L43
[3]
https://cmake.org/cmake/help/latest/variable/CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH.html
On Thu, Dec 30, 2021 at 2:35 PM Neil Okamoto <ne...@digitalfish.com> wrote:
> Hi Larry, thanks for that context. Agree, we wouldn't want to
> inadvertently break other people's builds. Sounds like the next step is to
> run some tests with an up-to-date release of oiio, and probably best to
> separate this question from that USD build script. I'll try to set aside
> some time to look at that.
>
_______________________________________________
Oiio-dev mailing list
Oiio-dev@lists.openimageio.org
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
