From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Ilmbase and openexr header files
Date: Mon, 07 Sep 2015 14:03:17 +0200 [thread overview]
Message-ID: <87fv2qwi62.fsf@gnu.org> (raw)
In-Reply-To: <20150906165156.GA9955@debian> (Andreas Enge's message of "Sun, 6 Sep 2015 18:52:22 +0200")
Andreas Enge <andreas@enge.fr> skribis:
> 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
This shouldn’t be a problem because:
--8<---------------cut here---------------start------------->8---
$ pkg-config OpenEXR --cflags
-pthread -I/gnu/store/bnp4nsy7v4lzw562k4v7w34jdg8vkc3s-openexr-2.2.0/include/OpenEXR -I/gnu/store/6ih7f5cq1amgh134f75xw2sxk39p9gi7-ilmbase-2.2.0/include/OpenEXR
--8<---------------cut here---------------end--------------->8---
> 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.
My guess is that Vigra doesn’t use pkg-config, and thus doesn’t get the
right -I flags.
Is that a correct guess? :-)
Thanks,
Ludo’.
next prev parent reply other threads:[~2015-09-07 12:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-06 16:52 Ilmbase and openexr header files Andreas Enge
2015-09-07 12:03 ` Ludovic Courtès [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fv2qwi62.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.