Changeset 2862

Timestamp:

Mar 30, 2009, 12:14:36 AM (16 years ago)

Author:

rgrieder

Message:

quote: "Fixed some bugs. Please do not break the code, when working with other people on one branch"
Me too. CMake wasn't even able to make the project after r2853!
The problem was the no -Wno-deprecated flag, which was set to all compilers.
Lets examine: There are three files with compiler settings: BuildConfig.cmake, BuildConfigGCC.cmake and BuildConfigMSVC.cmake. Suppose you want to apply a GCC specific option, which one do you pick? BuildConfig.cmake, exactly, because that only concerns GCC in contrast to BuildConfigGCC.cmake!
I still hope the dozens if not hundreds of hours of work spent on the build system to make it less of a mess weren't all that in vein…

• Also re enabled the OPTION to show extended compiler warnings and explicitly set it to false (which it was before, just not visibly).

Location:

code/branches/gui/cmake

Files:

• BuildConfig.cmake (modified) (2 diffs)
• BuildConfigGCC.cmake (modified) (1 diff)

code/branches/gui/cmake/BuildConfig.cmake

@@ -90 +90 @@
 ################ Compiler Config ################
 
-#OPTION(EXTRA_COMPILER_WARNINGS "Enable some extra warnings (heavily pollutes the output)")
+OPTION(EXTRA_COMPILER_WARNINGS "Enable some extra warnings (heavily pollutes the output)" FALSE)
 
 INCLUDE(FlagUtilities)
@@ -184 +184 @@
 # Disable Boost auto linking completely
 ADD_COMPILER_FLAGS("-DBOOST_ALL_NO_LIB")
-ADD_COMPILER_FLAGS("-Wno-deprecated")
 
 # If no defines are specified, these libs get linked statically

code/branches/gui/cmake/BuildConfigGCC.cmake

@@ -63 +63 @@
 ADD_COMPILER_FLAGS("-Wno-sign-compare" GCC_NO_SYSTEM_HEADER_SUPPORT CACHE)
 
+# For newer GCC (4.3 and above), don't display hundreds of annoying deprecated
+# messages. Other versions don't seem to show any such warnings at all.
+ADD_COMPILER_FLAGS("-Wno-deprecated")
+
 # Increase warning level if requested
 IF(EXTRA_COMPILER_WARNINGS)