1. 27 Apr, 2019 1 commit
  2. 26 Apr, 2019 1 commit
  3. 25 Apr, 2019 2 commits
  4. 24 Apr, 2019 5 commits
  5. 23 Apr, 2019 4 commits
  6. 22 Apr, 2019 10 commits
  7. 21 Apr, 2019 1 commit
  8. 20 Apr, 2019 1 commit
  9. 19 Apr, 2019 6 commits
    • Brad King's avatar
      MSVC: Do not add /W3 to CMAKE_<LANG>_FLAGS by default · 1baf122c
      Brad King authored
      We do not add default warning flags on other compilers, and having
      a warning flag in the default flags makes it hard for projects to
      customize the warning level.  They need to use string processing
      to remove `/W3` from `CMAKE_{C,CXX}_FLAGS`.  Therefore we should
      drop it.
      However, projects may be using string processing to replace `/W3`
      with another flag, so we cannot simply drop it.  Add a policy to
      drop it in a compatible way.
      Fixes: #18317
    • Brad King's avatar
      SunPro: Record support for C++14 features by SunPro 5.{14,15} · 66f3f11a
      Brad King authored
      SunPro 5.15 supports `-std=c++14` and several C++14 features.
      SunPro 5.14 accepts `-std=c++14` but does not update its definition of
      `__cplusplus` or any other macro to distinguish it from `-std=c++11`,
      so we need to blacklist a couple features that do work but that we
      cannot report for that version.  We can still support `cxx_std_14`.
      Co-Author: Robert Maynard <robert.maynard@kitware.com>
    • Brad King's avatar
      Merge branch 'vs-default-platform' into release-3.14 · cb733eb4
      Brad King authored
      Merge-request: !3246
    • Brad King's avatar
      VS: Provide the default platform name to project code · db02be85
      Brad King authored
      The value of `CMAKE_VS_PLATFORM_NAME` is computed by Visual Studio
      generators based on `CMAKE_GENERATOR_PLATFORM` or some default.
      Prior to the VS 2019 generator, the default was always `Win32`.
      However, for the `Visual Studio 16 2019` generator, the default is
      based on the host platform.
      Store the default in a new `CMAKE_VS_PLATFORM_NAME_DEFAULT` variable for
      use by project code.  This is particularly useful in toolchain files
      because they are allowed to set `CMAKE_GENERATOR_PLATFORM` and so
      `CMAKE_VS_PLATFORM_NAME` is not yet known.  Of course the toolchain file
      author knows whether it will set `CMAKE_GENERATOR_PLATFORM`, and if not
      then `CMAKE_VS_PLATFORM_NAME_DEFAULT` provides the platform name that
      will be used.
      Fixes: #19177
    • Brad King's avatar
      Merge topic 'test-find_package-resolve-symlinks' · 85421526
      Brad King authored
      a9428fc4 Tests: Fix FindPackageTest when path to source has a symlink
      e27437d0 Tests/FindPackageTest: Tell Git to ignore temporary symlink path
      Acked-by: Kitware Robot's avatarKitware Robot <kwrobot@kitware.com>
      Merge-request: !3244
    • Kitware Robot's avatar
      CMake Nightly Date Stamp · bf64e50d
      Kitware Robot authored
  10. 18 Apr, 2019 7 commits
  11. 17 Apr, 2019 2 commits
    • Brad King's avatar
      Merge topic 'msvc-runtime-library' · 2ed688a8
      Brad King authored
      fb3370b6 MSVC: Add abstraction for runtime library selection
      f621e7fa VS: Fix Fortran runtime library flag map special case for '-' options
      Acked-by: Kitware Robot's avatarKitware Robot <kwrobot@kitware.com>
      Acked-by: Ben Boeckel's avatarBen Boeckel <ben.boeckel@kitware.com>
      Acked-by: Leonid Pospelov's avatarLeonid Pospelov <pospelovlm@yandex.ru>
      Merge-request: !3211
    • Brad King's avatar
      MSVC: Add abstraction for runtime library selection · fb3370b6
      Brad King authored
      Replace our hard-coded defaults for `/MD` and `/MDd` with a first-class
      abstraction to select the runtime library from an enumeration of logical
      names.  We've long hesitated to do this because the idea of "runtime
      library selection" touches on related concepts on several platforms.
      Avoid that scope creep by simply defining an abstraction that applies
      only when targeting the MSVC ABI on Windows.
      Removing the old default flags requires a policy because existing
      projects may rely on string processing to edit them and choose a runtime
      library under the old behavior.  Add policy CMP0091 to provide
      Fixes: #19108