1. 30 Sep, 2019 1 commit
  2. 12 Jul, 2019 1 commit
  3. 30 May, 2019 1 commit
    • Brad King's avatar
      Do not exclude include directories made implicit by CPATH · 2d0b0e2b
      Brad King authored
      Entries of the `CPATH` environment variable are implicitly searched as
      include directories by some C/C++ compilers.  Since commit 5990ecb7
      (Compute implicit include directories from compiler output, 2018-12-07,
      v3.14.0-rc1~108^2) these entries are detected by CMake and included in
      the `CMAKE_{C,CXX}_IMPLICIT_INCLUDE_DIRECTORIES` variables.
      
      However, we should not exclude them from explicit specification via `-I`
      or particularly `-isystem` because they are meant as user-specified
      include directories that can be re-ordered without breaking compiler
      builtin headers.  In particular, we need explicit requests via
      `include_directories` with the `SYSTEM` option to result in `-isystem`
      so that third-party headers do not produce warnings.
      
      Co-Author: Ben Boeckel <ben.boeckel@kitware.com>
      Fixes: #19291
      2d0b0e2b
  4. 14 May, 2019 1 commit
    • Brad King's avatar
      Help: Add 3.14.4 release notes · f2aeba92
      Brad King authored
      Add a note about the fix in commit 3d371312 (target_link_libraries:
      Fix static library private deps in other dirs, 2019-04-30).  Also
      reference the equivalent note already added to the 3.13.5 notes.
      f2aeba92
  5. 19 Apr, 2019 1 commit
    • 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
      db02be85
  6. 26 Mar, 2019 1 commit
    • Brad King's avatar
      FindFontconfig: Convert module variables to camel case · a3a1e69f
      Brad King authored
      Our documented standard for find module variable names is to match the
      case of the find module package name.  This was overlooked when the
      module was added by commit 84e7920b (FindFontconfig: Add module to
      find Fontconfig, 2018-09-27, v3.14.0-rc1~523^2).
      
      The module was released with the upper case names in CMake 3.14.0, so
      fix it to have camel case names in 3.14.1.  This is incompatible but
      anyone using a given release series should be using the latest patch on
      it and we've made breaking fixups on newly released features like this
      before.
      Reported-by: Christophe Giboudeaux's avatarChristophe Giboudeaux <christophe@krop.fr>
      Fixes: #19094
      a3a1e69f
  7. 28 Feb, 2019 1 commit
  8. 26 Feb, 2019 1 commit
    • Brad King's avatar
      FindOctave: Remove module pending further work · 7a1f3fe0
      Brad King authored
      The `FindOctave` module added by commit 170bcb6f (FindOctave: Add
      module to find GNU octave, 2018-11-17, v3.14.0-rc1~283^2) has a few
      problems in its implementation that need to be worked out before the
      module can be included in a CMake release.  These were missed during
      review.  Remove the module for now.  It can be restored later with a
      fresh review.
      
      Issue: #18991
      7a1f3fe0
  9. 24 Feb, 2019 1 commit
  10. 21 Feb, 2019 1 commit
    • Craig Scott's avatar
      EXCLUDE_FROM_ALL: Don't warn if installing target excluded from all · d3b765d4
      Craig Scott authored
      The original warning pre-dates support for install components.
      There are now legitimate scenarios where an install(TARGETS)
      command may list a target that is excluded from all, e.g.
      hierarchical projects that will never install the component such a
      target belongs to.
      
      Fixes: #18938
      d3b765d4
  11. 17 Feb, 2019 1 commit
  12. 11 Feb, 2019 1 commit
  13. 08 Feb, 2019 1 commit
  14. 07 Feb, 2019 1 commit
  15. 06 Feb, 2019 2 commits