1. 22 Jan, 2019 1 commit
  2. 25 Sep, 2017 1 commit
  3. 09 Jun, 2017 1 commit
    • Brad King's avatar
      file(GENERATE): Add policy CMP0070 to define relative path behavior · 82be694c
      Brad King authored
      Previously `file(GENERATE)` did not define any behavior for relative
      paths given to the `OUTPUT` or `INPUT` arguments.  Define behavior
      consistent with CMake conventions and add a policy to provide
      compatibility for projects that relied on the old accidental behavior.
      Fixes: #16786
  4. 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'
  5. 24 Mar, 2017 1 commit
  6. 08 Nov, 2016 1 commit
  7. 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.
  8. 03 Sep, 2016 1 commit
  9. 29 Jun, 2016 1 commit
    • Brad King's avatar
      Avoid using KWSys auto_ptr by adopting it ourselves · b5ec5b09
      Brad King authored
      Replace use of cmsys::auto_ptr with a CM_AUTO_PTR macro that maps to
      our own implementation adopted from the KWSys auto_ptr implementation.
      Later we may be able to map CM_AUTO_PTR to std::auto_ptr on compilers
      that do not warn about it.
      Automate the client site conversions:
          git grep -l auto_ptr -- Source/ | grep -v Source/kwsys/ | xargs sed -i \
  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.
  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.
  12. 03 May, 2016 1 commit
  13. 29 Apr, 2016 1 commit
    • Brad King's avatar
      Source: Stabilize include order · 180538c7
      Brad King authored
      Each source file has a logical first include file.  Include it in an
      isolated block so that tools that sort includes do not move them.
  14. 01 Aug, 2015 1 commit
  15. 22 Apr, 2015 1 commit
  16. 09 Mar, 2015 1 commit
  17. 12 Nov, 2014 1 commit
    • Stephen Kelly's avatar
      file(GENERATE): Evaluate early to allow generating source files · b80557c7
      Stephen Kelly authored
      The evaluation files must be known before cmTargetTraceDependencies
      attempts to find them, but we must actually generate the files after
      cmTargetTraceDependencies, as that can add to target SOURCES.  The
      limitation is that the generated output name must not depend on the
      SOURCES of a target if the generated file is used by that target.
      Mark the output files as GENERATED so that trace dependencies does
      not expect them to already exist in the filesystem.
      Move the invokation of ForceLinkerLanguage in the Generate logic
      to after the generated file names are known.  ForceLinkerLanguage
      tries to determine the sources of a target (in order to determine
      an already-known language) and otherwise fails to get information
      about the generated file.
      Test that the output of file(GENERATE) can be used as a target source
      file and that accessing the target SOURCES in the name of the output
      file is an error.  Accessing the TARGET_OBJECTS would be a similar
      error if it was legal to use that generator expression in this
      context.  That is not currently possible and is a different error
      condition, so test the current error output as a reminder to change
      the expected output if that becomes possible in the future.  Test
      that generated rule files resulting from cmTargetTraceDependencies
      appear in the SOURCES generated in the output file.
  18. 04 Nov, 2014 1 commit
  19. 08 Mar, 2014 1 commit
  20. 24 May, 2013 1 commit
    • Stephen Kelly's avatar
      file: Add GENERATE command to produce files at generate time · b983a58b
      Stephen Kelly authored
      The idea is to write to a temp file which contains generator
      expressions, and at generate time, evaluate the generator expressions,
      and write the result to a file.
      Because executables on Windows are limited in the length of command line
      it is possible to use, it is common to write command line arguments to a
      file instead and specify the file as a source of arguments.
      This new FILE(GENERATE) subcommand allows the use of generator
      expressions to create such files so that they can be used with
      add_custom_command for example.