Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ImfHeader.h:22:10: fatal error: ImathVec.h: No such file or directory #1043

Open
sboehmann opened this issue Jun 6, 2021 · 4 comments · May be fixed by #1676
Open

ImfHeader.h:22:10: fatal error: ImathVec.h: No such file or directory #1043

sboehmann opened this issue Jun 6, 2021 · 4 comments · May be fixed by #1676

Comments

@sboehmann
Copy link

I am trying to update from 2.5.6 to 3.0.4. OpenEXR 3.0.4 builds, but my application no longer does. The error is:

.../include/OpenEXR/ImfHeader.h:22:10: fatal error: ImathVec.h: No such file or directory
   22 | #include "ImathVec.h"
      |          ^~~~~~~~~~~~

The reason is that I don't have <prefix>/include/OpenEXR and <prefix>/include/Imath in my include paths, only <prefix>/include.

@simogasp
Copy link

simogasp commented Jun 17, 2022

Imath provides both <prefix>/include/ and <prefix>/include/Imath as include directories, so it should be able to see the header

@lgritz
Copy link
Contributor

lgritz commented Jun 18, 2022

Yes, the fully qualified #include <Project/header.h> is always preferred in any context, IMHO.

@ianmasters
Copy link

Is this ever going to be fixed? Including without the Imath/ prefix does not work with VS2022 and vcpkg manifest mode. I have to fix up the header files whenever they are refreshed. If there's a better way or a way to include the Imath into the project's include directories I'd love to know. I've tried relative paths etc. but no luck.

@meshula
Copy link
Contributor

meshula commented Jul 23, 2023

Per @lgritz's comment, a PR implementing this change would be welcome.

@henri-gasc henri-gasc linked a pull request Mar 15, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants