Re: [Openexr-devel] warning: "ASSERT" redefined

[Florian Kainz]

Hi Nathan,

you are right, including ImfInputFile.h should not
automatically define an ASSERT macro.  You can avoid
the unwanted macro definition by editing the OpenEXR
source as follows (I will check corresponding changes
into the CVS repository):

 1) In IlmImf/ImfAttribute.h and IlmImf/ImfHeader.h,
    change the line that reads

        #include <Iex.h>
    to
        #include <IexBaseExc.h>

 2) In IlmImf/ImfXdr.h, change the line that reads

        #include <Iex.h>
    to
        #include <IexMathExc.h>

 3) Add the line

        #include <Iex.h>

    to the following files:

        IlmImf/ImfAttribute.cpp
        IlmImf/ImfHeader.cpp
        IlmImf/ImfOpaqueAttribute.cpp
        IlmImf/ImfRgbaFile.cpp
        IlmImf/ImfTiledRgbaFile.cpp
        IlmImfExamples/lowLevelIoExamples.cpp
        exrdisplay/loadImage.cpp

Hope this helps,

Florian


Nathan Kurz wrote:
> Hello ---
>
> I'm working with an application that has OpenEXR support, and I'm
> finding that the external OpenEXR headers seem to include some defines
> that probably should be used only internally within OpenEXR code.  In
> particular, including <OpenEXR/ImfInputFile.h> gives me this warning:
>
>   In file included from /usr/include/OpenEXR/Iex.h:48,
>                    from /usr/include/OpenEXR/ImfHeader.h:53,
>                    from /usr/include/OpenEXR/ImfInputFile.h:46,
>                    from fileexr.C:11:
>   /usr/include/OpenEXR/IexMacros.h:139:1: warning: "ASSERT" redefined
>
> I get this warning because I'm using ASSERT as a macro within my own
> code, but defined in a way that is appropriate for my application.
> Would it be possible that to have these internal macros kept more
> internally?  Or am I doing something wrong by including ImfInputFile?
>
> Thanks!
>
> Nathan Kurz
> address@hidden
>
>
>
> _______________________________________________
> Openexr-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/openexr-devel