1. 16 Aug, 2019 1 commit
  2. 18 Jul, 2019 1 commit
  3. 09 Jul, 2019 3 commits
  4. 16 May, 2019 1 commit
  5. 14 May, 2019 1 commit
  6. 28 Apr, 2019 1 commit
  7. 21 Mar, 2019 1 commit
  8. 16 Mar, 2019 1 commit
  9. 11 Mar, 2019 1 commit
  10. 21 Feb, 2019 1 commit
  11. 18 Jan, 2019 1 commit
    • Andrew Paprocki's avatar
      Fortran: Add compiler ID/Version generator expressions · a0809142
      Andrew Paprocki authored
      Adds `Fortran_COMPILER_ID` and `Fortran_COMPILER_VERSION` generator
      expression support to match equivalent `C_COMPILER_ID`,
      This is very helpful in the case where the C/C++ compiler suite is a
      different type of compiler from the platform Fortran compiler and
      projects use generator expressions to assign compiler flags and
      definitions.  (e.g. `GNU` C/C++ and `SunPro` Fortran on Linux)
  12. 02 Jan, 2019 1 commit
  13. 20 Dec, 2018 1 commit
    • Wouter Klouwen's avatar
      ExternalProject: add LOG_OUTPUT_ON_FAILURE option · 19d86e26
      Wouter Klouwen authored
      This option only has an effect if at least one of the other LOG_<step>
      options is enabled.  If an error occurs for a step which has logging to
      file enabled, that step's output will be printed to the console.  For
      cases where a large amount of output is recorded, just the end of that
      output may be printed to the console.
  14. 26 Oct, 2018 1 commit
  15. 19 Oct, 2018 2 commits
    • Wouter Klouwen's avatar
      ExternalProject: option LOG_MERGED_STDOUTERR to combine stdout and stderr · 7ddc9e35
      Wouter Klouwen authored
      In some circumstances the user of ExternalProject may not desire the
      split log files for stdout and stderr. In particular with a project has
      many errors it can be difficult to correlate the output error with the
      command that it resulted from.
      This commit adds the LOG_MERGED_STDOUTERR option that when enabled
      outputs into a unified <name>-<step>.log for each step. If disabled it
      will default to the previous behaviour of <name>-<step>-out.log and
    • Wouter Klouwen's avatar
      ExternalProject: add LOG_DIR option that allows overriding of log location · b6f6cac3
      Wouter Klouwen authored
      In some situations it can be helpful to separate out the location of the
      log files from the location of the stamp files. For instance if you have
      a continuous integration that exposes the location where log files are
      This commit adds an option that allows a user to override the default
      behaviour of putting the log files in STAMP_DIR called LOG_DIR. The
      previous behaviour of putting the log files into the STAMP_DIR applies
      if LOG_DIR is not specified.
  16. 29 Aug, 2018 1 commit
  17. 09 Jul, 2018 1 commit
    • Jeff Kowalski's avatar
      cmake-mode.el: Fix "unescaped character literals" warning · 67ae6da3
      Jeff Kowalski authored
      Emacs 27.0 warns
          Loading ‘cmake-mode’: unescaped character literals `?(', `?)' detected!
      during byte-compilation of cmake-mode.el The new warning was added in
      emacs commit c2bbdc3316 (Warn about missing backslashes during load).
      Add backslashes to escape the literals.
  18. 03 Jan, 2018 1 commit
  19. 18 Oct, 2017 2 commits
  20. 13 Oct, 2017 1 commit
  21. 27 Sep, 2017 1 commit
  22. 18 Sep, 2017 1 commit
    • Maarten de Vries's avatar
      vim: Remove default setting of expandtab · 0d543589
      Maarten de Vries authored
      An update from vim-cmake-syntax by commit v3.9.0-rc1~167^2^2
      (vim-cmake-syntax 2017-05-02, 2017-05-02) brought in a change to set
      `expandtab` in CMake language files.  This should be a per-project or
      per-user choice instead, so drop the setting.
  23. 10 Jul, 2017 2 commits
  24. 22 Jun, 2017 1 commit
  25. 05 Jun, 2017 1 commit
  26. 26 Apr, 2017 1 commit
  27. 23 Feb, 2017 1 commit
  28. 23 Jan, 2017 1 commit
  29. 15 Nov, 2016 1 commit
  30. 09 Nov, 2016 1 commit
  31. 27 Sep, 2016 1 commit
    • Brad King's avatar
      Simplify CMake per-source license notices · 86578ecc
      Brad King authored
      Per-source copyright/license notice headers that spell out copyright holder
      names and years are hard to maintain and often out-of-date or plain wrong.
      Precise contributor information is already maintained automatically by the
      version control tool.  Ultimately it is the receiver of a file who is
      responsible for determining its licensing status, and per-source notices are
      merely a convenience.  Therefore it is simpler and more accurate for
      each source to have a generic notice of the license name and references to
      more detailed information on copyright holders and full license terms.
      Our `Copyright.txt` file now contains a list of Contributors whose names
      appeared source-level copyright notices.  It also references version control
      history for more precise information.  Therefore we no longer need to spell
      out the list of Contributors in each source file notice.
      Replace CMake per-source copyright/license notice headers with a short
      description of the license and links to `Copyright.txt` and online information
      available from "https://cmake.org/licensing".  The online URL also handles
      cases of modules being copied out of our source into other projects, so we
      can drop our notices about replacing links with full license text.
      Run the `Utilities/Scripts/filter-notices.bash` script to perform the majority
      of the replacements mechanically.  Manually fix up shebang lines and trailing
      newlines in a few files.  Manually update the notices in a few files that the
      script does not handle.
  32. 19 Sep, 2016 1 commit
  33. 15 Sep, 2016 1 commit
  34. 17 Aug, 2016 2 commits