Le 2017-06-01 00:22, Danny Milosavljevic a écrit :
Hi Hartmut,
On Tue, 30 May 2017 16:48:38 +0200
Hartmut Goebel <h.goe...@crazy-compilers.com> wrote:
/gnu/store/…-openexr-2.2.0/include/OpenEXR/ImfInt64.h:44:24:
fatal error: ImathInt64.h: No such file or directory
but file …-openexr-2.2.0/include/OpenEXR/ImathInt64.h exists.
I discovered that OpenEXR/ImfInt64.h contains
#include "ImathInt64.h"
#include "ImfNamespace.h"
Maybe this should be "OpenEXR/ImathInt64.h" (same for the other)?
I think not. cpp (the C preprocessor) has no notion of modules and
what it does is just process #include "xx" relative to the directory
of the file it currently reads (the one containing the "#include"
directive), no matter how it went there. (If it can't find it then it
will fallback to the #include <xx> handler - but I think that's bad
form).
(If you wanted to specify the "OpenEXR/" you'd usually put
/gnu/store/…-openexr-2.2.0/include into the include path and include
it like this in OpenEXR/ImfInt64.h : #include <OpenEXR/ImathInt64.h>
with the <>)
Strange error message, though.
Is that gcc? Which version?
I've seen something similar already, openexr includes are divided in
ilmbase and openexr, so you need both inputs. See darktable in photo.scm
for an example.
