openexr

openexr copied to clipboard

Hi there;

I'm trying to follow along with the latest build instructions, and seem to be missing Half when building out the latest version of OpenEXR. I see mention of that component being split off into its own project, though that might not have been done yet. Is there a solution for building out OpenEXR in the interim?

Thank you!

The half type has indeed been split off into the Imath project, https://github.com/AcademySoftwareFoundation/imath, but it should be built automatically as an OpenEXR dependency. Can you say more about exactly what you're encountering?

Note also that there is no longer a separate "Half" library as there once was, the headers that define the half type are a part of the Imath library.

On Thu, Jan 14, 2021 at 8:54 PM Allen Hemberger [email protected] wrote:

Hi there;

I'm trying to follow along with the latest build instructions, and seem to be missing Half when building out the latest version of OpenEXR. I see mention of that component being split off into its own project, though that might not have been done yet. Is there a solution for building out OpenEXR in the interim?

Thank you!

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/AcademySoftwareFoundation/openexr/issues/900, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFC3DGMBOIQR3KGHUDCWXFTSZ7C7VANCNFSM4WDQFFTQ .

-- Cary Phillips | R&D Supervisor | ILM | San Francisco

Hi Cary! Thanks so much for responding!

The thing I'm ultimately trying to build here is Alembic, which cites openexr as a dependency, specifically for ilmbase. The Cmake scripts for Alembic require a path to Half, which is what triggered my original question, but it sounds like I should in fact point it to the resulting Imath library that the current openexr build generates...so I'll try that!

I should, then, clarify that openexr seems to build and install fine for me; its just that I was expecting different results.

Thank you!

There are gonna be some changes needed for downstream packages to adjust to some changes in openexr/imath 3.0 -- not just the split into two repos, but also some things have moved between individual libraries, headers shifted around, and a few other minor differences.

We don't actually expect a package that builds against openexr 2.x to be able to just get pointed at 3.x and build straight out of the box.

I'm trying to write a short "porting guide" based on my experience of having made the necessary changes to have OpenImageIO be able to build against either 2.x or 3.x. I'll try to get a draft of that written and submitted as a PR by the end of this weekend.

Understood, thanks very much Larry!

Hi again;

I'm trying to build this project (a dependency of yet another project I'm struggling to build), which seems to have a dependency on ILMbase as well. When I run cmake, I see errors that look like this.

I managed to get myself to this point by installing openexr (and, in turn, ilmbase) by way of vcpkg.

I'm not sure where to ask this question or how to troubleshoot it, but it seems somewhat related to the original question that brought me here (albeit I realize now that I'm not operating in openexr3.0 world, but back in openexr2.5, because that seems to be what vcpkg offers me). Is there a way for me to fix the errors I'm seeing in cmake such that I can press forward with my build?

Thanks so much!

https://github.com/AcademySoftwareFoundation/openvdb/pull/927

We are preparing for the 3.0 release. Hopefully vcpkg will follow quickly and this issue will be resolved.