<\/p>\n
Since CMake 3.2, it is possible to enforce in very simple way the use of c++11 features (see Craig Scott’s blog post<\/a> for more details). Until now in dtk, we had to test the architecture (Apple, Unix or Windows), then check whether the compiler provides c++11 support or not and eventually set dedicated flags manually.<\/p>\n <\/p>\n Here follows the code used in dtk:<\/p>\n One can see how painful and not really readable it was.<\/p>\n We now just have to add two variable definitions to enforce the use of c++11 features:<\/p>\n Obviously, this way is easier.<\/p>\n CMake provides finer tuning as far as the compiler features are concerned. Craig Scott details them very clearly in his post<\/a>. <\/p>\n <\/p>","protected":false},"excerpt":{"rendered":" Since CMake 3.2, it is possible to enforce in very simple way the use of c++11 features (see Craig Scott’s blog post for more details). Until now in dtk, we had to test the architecture (Apple, Unix or Windows), then check whether the compiler provides c++11 support or not and\u2026<\/p>\nFormer way<\/h2>\n
if(APPLE)\n set(CMAKE_CXX_FLAGS \"${CMAKE_CXX_FLAGS} -std=c++11 -I\/usr\/lib\/c++\/v1\")\nendif(APPLE)\n\nif(NOT APPLE AND NOT MSVC)\n\n include(CheckCXXCompilerFlag)\n CHECK_CXX_COMPILER_FLAG(\"-std=c++11\" COMPILER_SUPPORTS_CXX11)\n CHECK_CXX_COMPILER_FLAG(\"-std=c++0x\" COMPILER_SUPPORTS_CXX0X)\n\n if(COMPILER_SUPPORTS_CXX11)\n set(CMAKE_CXX_FLAGS \"${CMAKE_CXX_FLAGS} -std=c++11\")\n\n elseif(COMPILER_SUPPORTS_CXX0X)\n set(CMAKE_CXX_FLAGS \"${CMAKE_CXX_FLAGS} -std=c++0x\")\n\n else()\n message(STATUS \"The compiler ${CMAKE_CXX_COMPILER} has no C++11 support. Please use a different C++ compiler.\")\n endif()\n\nelse(NOT APPLE AND NOT MSVC)\n\n set(CMAKE_CXX_FLAGS \"${CMAKE_CXX_FLAGS}\")\n\nendif(NOT APPLE AND NOT MSVC)<\/code><\/pre>\nNew method<\/h2>\n
set(CMAKE_CXX_STANDARD 11)\nset(CMAKE_CXX_STANDARD_REQUIRED ON)<\/code><\/pre>\n