Open c-lipka opened 3 years ago
Looks like the OpenEXR library proper has finally been renamed from libIlmImf
to libOpenEXR
. So all we'll have to do is update the unix/config/ax_check_openexr.m4
automake script, and we should be fine.
Well, with that out of the way, we're running into th next snag, namely that what had once been the IlmBase component of OpenEXR has been moved out into a whole new library, Imath. So we might have to address that, too.
For now, I'll probably just throw that library off the list of those that we give credit to. We're not depending on them directly anyway. If we ever upgrade the version of OpenEXR bundled with POV-Ray for Windows, I might have a closer look how best to proceed.
... and plenty more cans of worms. I'm tabling this thing for now. We clearly have a problem with OpenEXR 3.0.
Addressed for v3.7.0 with pull request #422.
Addendum: In v3.7.0, using OpenEXR 3 may require specifying CXXFLAGS="-std=c++11"
when running the configure
script. We may or may not change this behavior in the future.
Addressed for v3.8.0 with pull request #423.
Will be addressed for v4.0 by (effectively or actually) merging the v3.8.0 branch at some later point in time.
Summary
On a GitHub Workflows runner I'm seeing configure failing to find ImfInputReadPixels in -lIlmImf, and therefore being unable to enable OpenEXR support during the build.
POV-Ray Version
Build Environment
Build Command Sequence
Pre-Build Output
Configure Output
Additional context (optional)
On GitHub Workflows runners using Ubuntu 18.04 or 20.04, and OpenEXR 2.0.2 and 2.3.0 respectively (unknown IlmImf versions), no such problem is seen.
Suggested Solution (optional)
We should examine whether this is a fundamental problem with OpenEXR 3.0.3 (possibly a change in 3.0.0), or whether it is due to an odd quirk of this particular machine.