openexr-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Openexr-devel] 2.2.0 release plans


From: Nick
Subject: Re: [Openexr-devel] 2.2.0 release plans
Date: Wed, 16 Jul 2014 22:50:10 -0700

My preferred method for dealing with zlib in exr on windows these days is to link to zlib statically. Since we no longer automagically export all symbols conflicts are no longer an issue. The advantages to not having yet another unversioned zlib in your path are huge and make exr usage much more robust since you don't have to worry about symbol/version cross pollution. It was a problem on Zeno at one point but wouldn't be any longer since all of exr is now decorated with exports. I'd recommend that we configure the exr build on Windows this way moving forward. 

- Nick

Sent from my iPhone

On 2014/07/16, at 11:47, "Ed Hanway" <address@hidden> wrote:

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: address@hidden [mailto: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

_______________________________________________
Openexr-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/openexr-devel
_______________________________________________
Openexr-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/openexr-devel

reply via email to

[Prev in Thread] Current Thread [Next in Thread]