From 5462659976b618a43493a09a3e5cfe043816ae94 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Simon=20B=C3=BCnzli?= Date: Fri, 18 Jul 2014 22:26:38 +0200 Subject: 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. --- source/fitz/error.c | 4 ---- 1 file changed, 4 deletions(-) (limited to 'source/fitz/error.c') diff --git a/source/fitz/error.c b/source/fitz/error.c index c5d98c92..e8225ee3 100644 --- a/source/fitz/error.c +++ b/source/fitz/error.c @@ -1,9 +1,5 @@ #include "mupdf/fitz.h" -#if defined(_WIN32) && !defined(NDEBUG) -#define USE_OUTPUT_DEBUG_STRING -#endif - #ifdef USE_OUTPUT_DEBUG_STRING #include #endif -- cgit v1.2.3