summaryrefslogtreecommitdiff
path: root/platform/win32/mudraw.vcproj
diff options
context:
space:
mode:
authorSimon Bünzli <zeniko@gmail.com>2014-07-18 22:26:38 +0200
committerTor Andersson <tor.andersson@artifex.com>2014-08-19 17:09:11 +0200
commit5462659976b618a43493a09a3e5cfe043816ae94 (patch)
tree012d98b59de08a986f0cabded8bc63113735d6c5 /platform/win32/mudraw.vcproj
parenta27c538cc3262377166251c73c9b09ff7f67192b (diff)
downloadmupdf-5462659976b618a43493a09a3e5cfe043816ae94.tar.xz
don't always write to Visual Studio's Output console in debug builds
We build MuPDF without NDEBUG defined in order to check assertions but don't want Visual Studio's Output console flooded with warnings for broken documents. So instead of always defining USE_OUTPUT_DEBUG_STRING for debug builds under Windows, allow the VS solutions to define it when desired and to omit it when not.
Diffstat (limited to 'platform/win32/mudraw.vcproj')
-rw-r--r--platform/win32/mudraw.vcproj4
1 files changed, 2 insertions, 2 deletions
diff --git a/platform/win32/mudraw.vcproj b/platform/win32/mudraw.vcproj
index b28291df..f3f8b511 100644
--- a/platform/win32/mudraw.vcproj
+++ b/platform/win32/mudraw.vcproj
@@ -40,7 +40,7 @@
Name="VCCLCompilerTool"
Optimization="0"
AdditionalIncludeDirectories="..\..\include"
- PreprocessorDefinitions="DEBUG=1"
+ PreprocessorDefinitions="DEBUG=1;USE_OUTPUT_DEBUG_STRING"
MinimalRebuild="true"
BasicRuntimeChecks="3"
RuntimeLibrary="1"
@@ -186,7 +186,7 @@
Name="VCCLCompilerTool"
Optimization="0"
AdditionalIncludeDirectories="..\..\include"
- PreprocessorDefinitions="MEMENTO=1;DEBUG=1"
+ PreprocessorDefinitions="MEMENTO=1;DEBUG=1;USE_OUTPUT_DEBUG_STRING"
MinimalRebuild="true"
BasicRuntimeChecks="3"
RuntimeLibrary="1"