1. 08 Jul, 2019 1 commit
  2. 14 Feb, 2019 3 commits
  3. 22 Jan, 2019 1 commit
  4. 20 Apr, 2018 2 commits
    • Brad King's avatar
      Fortran: Add support for submodule dependencies · 40273531
      Brad King authored
      Since commit v3.7.0-rc1~73^2~1 (Fortran: Add support for submodule
      syntax in dependency scanning, 2016-09-05) we support parsing Fortran
      sources that use submodule syntax, but it left addition of `.smod`
      dependencies to future work.  Add it now.
      
      The syntax
      
          submodule (module_name) submodule_name
      
      means the current source requires `module_name.mod` and provides
      `module_name@submodule_name.smod`.  The syntax
      
          submodule (module_name:submodule_name) nested_submodule_name
      
      means the current source requires `module_name@submodule_name.smod`
      provides `module_name@nested_submodule_name.smod`.
      
      Fixes: #17017
      40273531
    • Brad King's avatar
      Fortran: Refactor to treat .mod extension as part of module name · 62538b2c
      Brad King authored
      When tracking module names internally, include the `.mod` extension.
      This will later be useful to distinguish them from `.smod` extensions
      for submodules.
      62538b2c
  5. 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
  6. 15 Sep, 2017 1 commit
  7. 12 Sep, 2017 1 commit
  8. 27 Aug, 2017 1 commit
  9. 26 Aug, 2017 1 commit
  10. 24 Aug, 2017 1 commit
  11. 11 Apr, 2017 1 commit
    • Daniel Pfeifer's avatar
      Use quotes for non-system includes · 1d829c86
      Daniel Pfeifer authored
      Automate with:
      
      git grep -l '#include <cm_' -- Source \
        | xargs sed -i 's/#include <\(cm_.*\)>/#include "\1"/g'
      
      git grep -l '#include <cmsys/' -- Source \
        | xargs sed -i 's/#include <\(cmsys\/.*\)>/#include "\1"/g'
      
      git grep -l '#include <cm[A-Z]' -- Source \
        | xargs sed -i 's/#include <\(cm[A-Z].*\)>/#include "\1"/g'
      1d829c86
  12. 29 Mar, 2017 1 commit
  13. 12 Dec, 2016 1 commit
  14. 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
  15. 06 Sep, 2016 2 commits
  16. 03 Sep, 2016 1 commit
  17. 18 Aug, 2016 1 commit
  18. 16 Aug, 2016 1 commit
  19. 28 Jun, 2016 1 commit
  20. 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
  21. 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
  22. 05 Apr, 2016 1 commit
    • Brad King's avatar
      cmFortranParser: Skip #line directives that do not name files · f831d752
      Brad King authored
      Since commit v3.5.0-rc1~241^2~1 (cmFortranParser: Parse #line
      directives, 2015-11-02) our Fortran dependency scanner parses `#line`
      directives to extract the named files.  However, some compilers produce
      `#line` directives that name directories instead of files.  Work around
      such cases by verifying that the extracted path names a file and not a
      directory.
      f831d752
  23. 02 Nov, 2015 1 commit
    • Brad King's avatar
      cmFortranParser: Parse #line directives · ba819f49
      Brad King authored
      Teach the lexer to extract the #line directive prefix and line number as
      a new token type.  Teach the parser to recognize this token followed by
      a string as the file name (plus possibly other content).  Report the
      named file as included by the source file.
      ba819f49
  24. 27 Jul, 2015 1 commit