1. 13 Feb, 2018 1 commit
  2. 31 Jan, 2018 1 commit
    • Pavel Solodovnikov's avatar
      Reduce raw string pointers usage. · 653b8946
      Pavel Solodovnikov authored
      * Change some functions to take `std::string` instead of
        `const char*` in the following classes: `cmMakeFile`, `cmake`,
        `cmCoreTryCompile`, `cmSystemTools`,  `cmState`, `cmLocalGenerator`
        and a few others.
      * Greatly reduce using of `const char*` overloads for
        `cmSystemTools::MakeDirectory` and `cmSystemTools::RelativePath`.
      * Remove many redundant `c_str()` conversions throughout the code.
      653b8946
  3. 29 Jan, 2018 1 commit
  4. 24 Jan, 2018 1 commit
  5. 23 Jan, 2018 2 commits
  6. 12 Jan, 2018 2 commits
    • Brad King's avatar
      Genex: Enable COMPILE_LANGUAGE for INCLUDE_DIRECTORIES with VS and Xcode · 506fda1c
      Brad King authored
      The set of compile flags used for a target's C and C++ sources is based
      on the linker language.  By default this is always the C++ flags if any
      C++ sources appear in the target, and otherwise the C flags.  Therefore
      we can define the `COMPILE_LANGUAGE` generator expression in
      `INCLUDE_DIRECTORIES` to match the selected language.
      
      This is not exactly the same as for other generators, but is the best VS
      and Xcode can do.  It is also sufficient for many use cases since the
      set of include directories for C and C++ is frequently similar but may
      be distinct from those for other languages like CUDA.
      
      Fixes: #17435
      506fda1c
    • Brad King's avatar
      Genex: Enable COMPILE_LANGUAGE for COMPILE_DEFINITIONS with VS and Xcode · c2f79c98
      Brad King authored
      The set of compile flags used for a target's C and C++ sources is based
      on the linker language.  By default this is always the C++ flags if any
      C++ sources appear in the target, and otherwise the C flags.  Therefore
      we can define the `COMPILE_LANGUAGE` generator expression in
      `COMPILE_DEFINITIONS` to match the selected language.
      
      This is not exactly the same as for other generators, but is the best VS
      and Xcode can do.  It is also sufficient for many use cases since the
      set of definitions for C and C++ is frequently similar but may be
      distinct from those for other languages like CUDA.
      
      Issue: #17435
      c2f79c98
  7. 03 Jan, 2018 1 commit
  8. 22 Dec, 2017 2 commits
  9. 13 Dec, 2017 1 commit
  10. 05 Dec, 2017 1 commit
  11. 04 Dec, 2017 1 commit
  12. 20 Nov, 2017 1 commit
  13. 15 Nov, 2017 1 commit
  14. 10 Nov, 2017 1 commit
    • Craig Scott's avatar
      Xcode: use ranged for loops, cleanup existing for loops · 98cbcedd
      Craig Scott authored
      The changes are mostly converting old-style explicit iterator for loops
      into ranged for statements. A number of for loops had already been
      changed over, but local variables had been left behind instead of being
      absorbed into the ranged for statement, so these have been cleaned up
      too. A couple of minor improvements were made in areas already being
      updated by the for loop changes to slightly simplify the code or to
      avoid unnecessary conversions between `const char*` and `std::string`.
      98cbcedd
  15. 09 Nov, 2017 1 commit
  16. 31 Oct, 2017 1 commit
  17. 30 Oct, 2017 1 commit
  18. 18 Oct, 2017 1 commit
    • Brad King's avatar
      VS,Xcode: Add CMakeLists.txt sources without mutating targets · 344d149a
      Brad King authored
      Rather than injecting `CMakeLists.txt` files into each target's
      `SOURCES`, teach the generators to add them during generation using
      dedicated code.  This avoids mutating the original targets, and avoids
      polluting `$<TARGET_PROPERTY:foo,SOURCES>` with generator-specific
      content.
      
      This also avoids listing the `CMakeLists.txt` sources in the results of
      `CMAKE_DEBUG_TARGET_PROPERTIES==SOURCES` so the `RunCMake.TargetSources`
      test no longer needs a separate case for IDEs.
      344d149a
  19. 13 Oct, 2017 1 commit
  20. 03 Oct, 2017 1 commit
  21. 28 Sep, 2017 7 commits
  22. 25 Sep, 2017 1 commit
  23. 19 Sep, 2017 1 commit
  24. 15 Sep, 2017 1 commit
    • Brad King's avatar
      Use C++11 override instead of CM_OVERRIDE · 0b33aee4
      Brad King authored
      We now require C++11 support including `override`.  Drop use of
      the old compatibility macro.  Convert references as follows:
      
          git grep -l CM_OVERRIDE -- '*.h' '*.hxx' '*.cxx' |
            xargs sed -i 's/CM_OVERRIDE/override/g'
      0b33aee4
  25. 30 Aug, 2017 1 commit
  26. 24 Aug, 2017 2 commits
    • Daniel Pfeifer's avatar
      Use C++11 nullptr · 5962db43
      Daniel Pfeifer authored
      5962db43
    • Brad King's avatar
      Xcode: Revert addition of "outputPaths" to custom command build phase · 9ecee256
      Brad King authored
      The change in commit v3.9.0~3^2 (Xcode: Add "outputPaths" to custom
      command script build phase, 2017-07-13) was meant to support Xcode 9's
      new build system.  However, without matching "inputPaths", Xcode will
      not re-run the build phase if its outputs have already been generated.
      This broke the old Xcode build system too.
      
      Revert the change for now so at least the old Xcode build system works.
      Further investigation will be needed to add proper support for Xcode 9's
      new build system.
      
      Fixes: #17178
      9ecee256
  27. 18 Aug, 2017 1 commit
  28. 14 Jul, 2017 1 commit
  29. 29 Jun, 2017 1 commit
  30. 28 Jun, 2017 1 commit