From ca4e840155e03ed85acd3219cd15f792c5025bb4 Mon Sep 17 00:00:00 2001 From: Robert Osfield Date: Tue, 2 Jul 2013 14:35:29 +0000 Subject: [PATCH] From Laurens Voerman, "With fstream inheritaince now removed the warning can be enabled again." --- CMakeLists.txt | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/CMakeLists.txt b/CMakeLists.txt index bc92f30bc..9257a210b 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -800,14 +800,11 @@ IF(CMAKE_COMPILER_IS_GNUCXX) ELSEIF(MSVC) - # FIXME: What are good aggressive warning flags for Visual Studio? - # And do we need to further subcase this for different versions of VS? - # CMake variables: MSVC60, MSVC70, MSVC71, MSVC80, CMAKE_COMPILER_2005 + #disable specific warning level 4 warnings: + #C4100 'identifier' : unreferenced formal parameter + #C4127 Error Message conditional expression is constant + #C4706 assignment within conditional expression SET(OSG_AGGRESSIVE_WARNING_FLAGS /W4 /wd4706 /wd4127 /wd4100) - IF(MSVC11) - SET(OSG_AGGRESSIVE_WARNING_FLAGS ${OSG_AGGRESSIVE_WARNING_FLAGS} /wd4250) - ENDIF() - ELSEIF(CMAKE_CXX_COMPILER_ID STREQUAL "Clang") SET(OSG_AGGRESSIVE_WARNING_FLAGS -Wall -Wparentheses -Wno-long-long -Wno-import -pedantic -Wreturn-type -Wmissing-braces -Wunknown-pragmas -Wunused -Wno-overloaded-virtual)