1. 23 May, 2019 1 commit
  2. 06 Feb, 2019 1 commit
  3. 22 Jan, 2019 1 commit
  4. 01 Jun, 2018 1 commit
    • Kitware Robot's avatar
      Revise C++ coding style using clang-format-6.0 · d7204e64
      Kitware Robot authored
      Run the `clang-format.bash` script to update all our C and C++ code to a
      new style defined by `.clang-format`.  Use `clang-format` version 6.0.
      
      * If you reached this commit for a line in `git blame`, re-run the blame
        operation starting at the parent of this commit to see older history
        for the content.
      
      * See the parent commit for instructions to rebase a change across this
        style transition commit.
      d7204e64
  5. 21 Feb, 2018 1 commit
  6. 30 Aug, 2017 1 commit
  7. 12 Dec, 2016 1 commit
  8. 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.
      86578ecc
  9. 03 Sep, 2016 1 commit
  10. 16 May, 2016 1 commit
    • Kitware Robot's avatar
      Revise C++ coding style using clang-format · d9fd2f54
      Kitware Robot authored
      Run the `Utilities/Scripts/clang-format.bash` script to update
      all our C++ code to a new style defined by `.clang-format`.
      Use `clang-format` version 3.8.
      
      * If you reached this commit for a line in `git blame`, re-run the blame
        operation starting at the parent of this commit to see older history
        for the content.
      
      * See the parent commit for instructions to rebase a change across this
        style transition commit.
      d9fd2f54
  11. 09 May, 2016 1 commit
    • Brad King's avatar
      Remove `//------...` horizontal separator comments · 0ac18d40
      Brad King authored
      Modern editors provide plenty of ways to visually separate functions.
      Drop the explicit comments that previously served this purpose.
      Use the following command to automate the change:
      
          $ git ls-files -z -- \
              "*.c" "*.cc" "*.cpp" "*.cxx" "*.h" "*.hh" "*.hpp" "*.hxx" |
            egrep -z -v "^Source/cmCommandArgumentLexer\." |
            egrep -z -v "^Source/cmCommandArgumentParser(\.y|\.cxx|Tokens\.h)" |
            egrep -z -v "^Source/cmDependsJavaLexer\." |
            egrep -z -v "^Source/cmDependsJavaParser(\.y|\.cxx|Tokens\.h)" |
            egrep -z -v "^Source/cmExprLexer\." |
            egrep -z -v "^Source/cmExprParser(\.y|\.cxx|Tokens\.h)" |
            egrep -z -v "^Source/cmFortranLexer\." |
            egrep -z -v "^Source/cmFortranParser(\.y|\.cxx|Tokens\.h)" |
            egrep -z -v "^Source/cmListFileLexer\." |
            egrep -z -v "^Source/cm_sha2" |
            egrep -z -v "^Source/(kwsys|CursesDialog/form)/" |
            egrep -z -v "^Utilities/(KW|cm).*/" |
            xargs -0 sed -i '/^\(\/\/---*\|\/\*---*\*\/\)$/ {d;}'
      
      This avoids modifying third-party sources and generated sources.
      0ac18d40
  12. 18 Jan, 2015 1 commit
  13. 12 Dec, 2014 1 commit
  14. 21 Oct, 2013 1 commit
    • Rolf Eike Beer's avatar
      use size_t for GeneratorExpressionContent::ContentLength to fix some warnings · a80fe4b1
      Rolf Eike Beer authored
      CMake/Source/cmGeneratorExpressionParser.cxx: In member function ‘void cmGeneratorExpressionParser::ParseGeneratorExpression(std::vector<cmGeneratorExpressionEvaluator*>&)’:
      CMake/Source/cmGeneratorExpressionParser.cxx:116:55: warning: conversion to ‘unsigned int’ from ‘long int’ may alter its value [-Wconversion]
      CMake/Source/cmGeneratorExpressionParser.cxx:240:39: warning: conversion to ‘int’ from ‘long int’ may alter its value [-Wconversion]
      a80fe4b1
  15. 13 Aug, 2013 1 commit
  16. 27 Nov, 2012 1 commit
    • Stephen Kelly's avatar
      Genex: Don't segfault on $<FOO,> · b581be07
      Stephen Kelly authored
      Treat the comma as part of the identifier here. It will later not
      resolve to a generator expression and the user gets a proper error
      message.
      b581be07
  17. 17 Oct, 2012 4 commits
  18. 09 Oct, 2012 2 commits
    • Stephen Kelly's avatar
      GenEx: Parse comma after colon tokens specially · b3d8f5da
      Stephen Kelly authored
      Otherwise the comma is treated as plain text by ParseContent.
      
      $<STREQUAL:,> should be valid and true.
      $<STREQUAL:,something> should be valid and false.
      
      $<STREQUAL:,,> should be non-valid as it is 3 parameters.
      $<STREQUAL:something,,> should be non-valid as it is 3 parameters.
      
      Additionally, this allows reporting the correct error for other
      expressions. For example $<TARGET_PROPERTY:,> should be invalid
      because it has an empty target and empty property. It shouldn't
      attempt to read the property ',' on the 'implicit this' target.
      b3d8f5da
    • Stephen Kelly's avatar
      GenEx: It is not an error to specify an empty parameter · 4801eb63
      Stephen Kelly authored
      This is allowed by the CONFIG and STREQUAL expressions.
      4801eb63
  19. 21 Sep, 2012 1 commit
  20. 18 Sep, 2012 1 commit
    • Stephen Kelly's avatar
      cmGeneratorExpression: Re-write for multi-stage evaluation · f1eacf0e
      Stephen Kelly authored
      The expressions may be parsed and then cached and evaluated multiple
      times.  They are evaluated lazily so that literals such as ',' can be
      treated as universal parameter separators, and can be processed from
      results without appearing literally, and without interfering with the
      parsing/evaluation of the entire expression.
      f1eacf0e