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.



On Jul 16, 2014, at 10:22 AM, Karl Rasche <[email protected]> wrote:

> Not being a cmake guru, how feasible would it be to define NOMINMAX in the 
> generated project files' preprocessor settings?  That sounds nicer than a 
> hardcoded #define NOMINMAX.
> 
> Karl
> 
> On Wednesday, July 16, 2014, Mike Wong | ax.gmail <[email protected]> wrote:
> Concerning min/max macros problem on windows, here's the suggested fix from 
> M$ :
> 
> http://support.microsoft.com/kb/143208
> 
> 
> On Tue, Jul 15, 2014 at 7:06 PM, Thorsten Kaufmann 
> <[email protected]> wrote:
> So i fixed all of them in my fork and added a pull request: 
> https://github.com/openexr/openexr/pull/103
> 
>  
> 
> Compiles cleanly for me on win7 x64 vs 2013 express
> 
>  
> 
> Cheers,
> 
> Thorsten
> 
>  
> 
>  
> Thorsten Kaufmann
> Production Pipeline Architect 
> 
> Mackevision Medien Design GmbH
> Forststraße 7
> 70174 Stuttgart
> 
> T  T +49 711 93 30 48 606
> F  +49 711 93 30 48 90
> M +49 151 19 55 55 02
> 
> [email protected]
> www.mackevision.de
> 
> Geschäftsführer: Armin Pohl, Joachim Lincke, Karin Suttheimer
> HRB 243735 Amtsgericht Stuttgart
> 
> 
> _______________________________________________
> Openexr-devel mailing list
> [email protected]
> https://lists.nongnu.org/mailman/listinfo/openexr-devel

--
Larry Gritz
[email protected]



_______________________________________________
Openexr-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/openexr-devel

Reply via email to