1. 10 Jul, 2017 1 commit
  2. 27 Jun, 2017 2 commits
    • Brad King's avatar
      CMake 3.9.0-rc5 · 372de3f8
      Brad King authored
      372de3f8
    • Brad King's avatar
      VS: Fix support for nvcc flags not in our flag table · bbc1f364
      Brad King authored
      The change in commit v3.9.0-rc4~3^2 (VS: Improve workaround for CUDA
      -Xcompiler placement bug, 2017-06-21) accidentally appended to the
      `AdditionalOptions` as if it were a `;`-separated list, but it is
      actually a command-line string.  Append with a space instead.
      
      While at it, fix the same problem for the `AdditionalOptions` added to
      `CudaLink` by commit v3.9.0-rc3~1^2 (CUDA: When linking device code
      suppress CUDA 8.0+ deprecation warnings, 2017-06-09).
      
      Fixes: #17008
      bbc1f364
  3. 26 Jun, 2017 1 commit
  4. 22 Jun, 2017 2 commits
    • Brad King's avatar
      CMake 3.9.0-rc4 · 8fe54172
      Brad King authored
      8fe54172
    • Brad King's avatar
      VS: Fix support for rc /nologo flag in per-source COMPILE_FLAGS · 974f4333
      Brad King authored
      Since commit v3.9.0-rc1~160^2 (VS: Use tool-specific flag table for
      COMPILE_FLAGS parsing, 2017-05-03) we now correctly use the `rc` flag
      table to process the COMPILE_FLAGS flags of `.rc` source files instead
      of incorrectly using the `cl` flag table as before.  However, our `rc`
      flag table is not complete.  The `/nologo` flag was working before only
      by accident because the `cl` flag table entry for it happened to match.
      Add the proper entry to the `rc` flag table.
      
      Fixes: #16991
      974f4333
  5. 21 Jun, 2017 3 commits
    • Brad King's avatar
      VS: Improve workaround for CUDA -Xcompiler placement bug · 3b754215
      Brad King authored
      In commit v3.9.0-rc1~431^2~6 (VS: Place CUDA host compiler options in
      proper project file fields, 2017-03-07) we worked around a bug in the
      CUDA VS integration by dropping `AdditionalCompilerOptions`.  However,
      this silently drops `-Xcompiler=` options given by the user that don't
      map to one of CudaCompile's dedicated settings.  Improve the workaround
      to instead put the remaining `AdditionalCompilerOptions` into the
      `AdditionalOptions` field behind `-Xcompiler=` ourselves.
      3b754215
    • Brad King's avatar
      VS: Fix target_compile_options for CUDA · f2059585
      Brad King authored
      Fix the VS generator to honor `COMPILE_OPTIONS` for CUDA.  The exclusion
      added by commit v3.9.0-rc1~431^2~7 (VS: Do not pass CUDA compile options
      to C compiler, 2017-03-07) was correct but we need additional logic to
      pass the CUDA compile options to the CUDA compiler.  Also we should
      still pass the CXX or C options to MSVC (ClCompile) when those languages
      are enabled even if the link language is CUDA.
      f2059585
    • Michael Stürmer's avatar
      Vs: allow CSharp targets to be linked to CXX targets · 51865fc6
      Michael Stürmer authored
      Fixes: #16755
      51865fc6
  6. 14 Jun, 2017 2 commits
    • Brad King's avatar
      cmake: Fix default file translate mode when using libuv · 871adefc
      Brad King authored
      On Windows, libuv's one-time initialization changes the C runtime
      library's  `_fmode` setting to `_O_BINARY`, thus causing files to open
      as binary after that instead of the default `_O_TEXT` mode.  See
      upstream libuv issue 840.  Work around the problem by performing libuv
      initialization early and then restoring `_fmode`.
      
      In particular, this currently affects server mode.  Without this fix,
      the `_fmode` setting changes when the server mode initializes libuv.
      
      Fixes: #16962
      871adefc
    • Brad King's avatar
      IPO: Consider support for each language separately · ba247cca
      Brad King authored
      We only define `INTERPROCEDURAL_OPTIMIZATION` behavior for C, CXX, and
      Fortran languages.  Do not try to enable support for other languages.
      Furthermore, each language builds with a different compiler, so check
      for support by CMake and the compiler for each language independently.
      
      Fixes: #16944
      ba247cca
  7. 13 Jun, 2017 2 commits
  8. 08 Jun, 2017 1 commit
  9. 07 Jun, 2017 2 commits
  10. 06 Jun, 2017 1 commit
  11. 05 Jun, 2017 2 commits
  12. 04 Jun, 2017 1 commit
  13. 03 Jun, 2017 4 commits
  14. 02 Jun, 2017 2 commits
  15. 01 Jun, 2017 5 commits
  16. 31 May, 2017 3 commits
    • Brad King's avatar
      Ninja: Fix CMP0058 on MinGW · 82badfff
      Brad King authored
      For CMP0058 we identify dependencies that have no rules to generate them
      by collecting a set of all dependencies and a set of all files CMake
      knows are generated by something, and then computing a set difference.
      Fix construction of these sets to use the same form for each path.
      This is after ConvertToNinjaPath but before EncodePath.
      
      Without this, the slash conversion done by EncodePath for the GNU
      compiler on Windows results in a mismatch, triggering an incorrect
      CMP0058 warning.
      82badfff
    • Brad King's avatar
      CMake 3.8.2 · 0d5a2252
      Brad King authored
      0d5a2252
    • Kitware Robot's avatar
      CMake Nightly Date Stamp · b3379e63
      Kitware Robot authored
      b3379e63
  17. 30 May, 2017 5 commits
  18. 29 May, 2017 1 commit