Explicitly define NOMINMAX to avoid conflict with the 'max' macro definition
Review Request #127729 - Created April 23, 2016 and discarded
|Andrius da Costa Ribas|
Although there is currently no problem on building kcoreaddons, when building okular (and possibly other apps) the compiler gets confused when it reaches std::numeric_limits<uint>::max() as <windows.h> is also included and it defines a 'max' macro.
Okular is buildable on MSVC after this patch. No further testing done.