From: Andreas Enge <andreas@enge.fr>
To: guix-devel@gnu.org
Subject: Ilmbase and openexr header files
Date: Sun, 6 Sep 2015 18:52:22 +0200 [thread overview]
Message-ID: <20150906165156.GA9955@debian> (raw)
Hello,
the openexr package has ilmbase as a propagated input, since the openexr
header files include ilmbase header files. However, there is a problem with
subdirectories, since both packages put the include files into
.../include/OpenEXR.
Then, for instance,
/gnu/store/bnp4nsy7v4lzw562k4v7w34jdg8vkc3s-openexr-2.2.0/include/OpenEXR/ImfInt64.h
contains a line
#include "ImathInt64.h"
This is the file
/gnu/store/6ih7f5cq1amgh134f75xw2sxk39p9gi7-ilmbase-2.2.0/include/OpenEXR/ImathInt64.h
which of course is not found, since it resides in the subdirectory OpenEXR.
(Well, I wonder whether things work when everything is installed together in
/usr/include/OpenEXR, but anyway this is not our case.)
There was an error when adding openexr support to vigra, which I repaired
with a kludge, and it is happening again in the package hugin that I am
preparing. So I wonder what would be the proper fix.
I see the following options:
1) In vigra, I added ilmbase explicitly as an input and a configure-flag
(string-append "-DCMAKE_CXX_FLAGS=-I"
(assoc-ref %build-inputs "ilmbase")
"/include/OpenEXR"))))
which adds the correct include directory with an "-I" option during
compilation.
2) One might modify the environment variable CPATH in a separate phase
by adding the OpenEXR subdirectory of ilmbase.
3) One might also patch the openexr header files, replacing
#include "Imath...
by
#include "OpenEXR/Imath...
To me, 3) looks like the proper fix. What do you think?
Andreas
next reply other threads:[~2015-09-06 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-06 16:52 Andreas Enge [this message]
2015-09-07 12:03 ` Ilmbase and openexr header files Ludovic Courtès
2015-09-07 13:38 ` Andreas Enge
2015-09-07 15:56 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150906165156.GA9955@debian \
--to=andreas@enge.fr \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).