1. 03 Feb, 2018 1 commit
  2. 01 Feb, 2018 1 commit
  3. 29 Jan, 2018 3 commits
  4. 26 Jan, 2018 1 commit
  5. 25 Jan, 2018 1 commit
  6. 24 Jan, 2018 3 commits
  7. 23 Jan, 2018 3 commits
  8. 22 Jan, 2018 1 commit
  9. 20 Jan, 2018 1 commit
  10. 19 Jan, 2018 1 commit
  11. 18 Jan, 2018 2 commits
  12. 17 Jan, 2018 2 commits
  13. 16 Jan, 2018 1 commit
  14. 15 Jan, 2018 1 commit
  15. 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
  16. 10 Jan, 2018 3 commits
  17. 08 Jan, 2018 7 commits
  18. 03 Jan, 2018 1 commit
  19. 02 Jan, 2018 1 commit
  20. 27 Dec, 2017 1 commit
    • Craig Scott's avatar
      execute_process: Allow UTF-8 as a synonym for the UTF8 keyword · 8caec41e
      Craig Scott authored
      UTF-8 is the proper naming according to the UTF-8 RFC and is also the
      name used for a similar keyword in the file() command. This commit
      brings (backward compatible) consistency to the keyword names and allows
      the standard UTF-8 name to be used with execute_process(). The old UTF8
      keyword is still supported.
      8caec41e
  21. 22 Dec, 2017 1 commit
  22. 15 Dec, 2017 2 commits