Re: [Openexr-devel] 2.2.0 release plans

[Ed Hanway]

I believe it's only when using USE_ZLIB_WINAPI that the min/max issue happens.  With that option enabled, zlib.h drags in the windows headers, causing the conflict.  There are places in IlmBase that use windows includes directly (IlmThread) already use the #define NOMINMAX prior to the include to avoid this.

 

Question: does anybody really count on the USE_ZLIB_WINAPI option?

 

From: openexr-devel-bounces+address@hidden [mailto:openexr-devel-bounces+address@hidden On Behalf Of Karl Rasche
Sent: Wednesday, July 16, 2014 11:08 AM
To: Larry Gritz
Cc: address@hidden
Subject: Re: [Openexr-devel] 2.2.0 release plans

 

It sure looks like std::min/max usage is contained to within .cpp files.

 

There's a variety of other places that use the same functions - but only IlmDwaCompressor.cpp was causing problems? That seems a bit wierd.

 

Karl

On Wednesday, July 16, 2014, Larry Gritz <address@hidden> wrote:

Another application that uses the OpenEXR libraries will #include the OpenEXR headers, but will not actually use the OpenEXR build system and its command line preprocessor settings.

 

So if this issue extends to any of the header files, you need to fix it in the headers, or it'll be broken in the user's app