1. 14 Jul, 2019 1 commit
  2. 26 Oct, 2017 1 commit
    • Deniz Bahadir's avatar
      Teach target_* commands to set INTERFACE properties of IMPORTED targets · fe4b25ec
      Deniz Bahadir authored
      Now, several `INTERFACE_*` properties can be set on `IMPORTED` targets,
      not only via `set_property` and `set_target_properties` but also via
      `target_compile_definitions`, `target_compile_features`,
      `target_compile_options`, `target_include_directories`, `target_sources`
      and `target_link_libraries`.
      
      Fixes: #15689
      Issue: #17197
      fe4b25ec
  3. 15 Sep, 2017 1 commit
    • Brad King's avatar
      Use C++11 override instead of CM_OVERRIDE · 0b33aee4
      Brad King authored
      We now require C++11 support including `override`.  Drop use of
      the old compatibility macro.  Convert references as follows:
      
          git grep -l CM_OVERRIDE -- '*.h' '*.hxx' '*.cxx' |
            xargs sed -i 's/CM_OVERRIDE/override/g'
      0b33aee4
  4. 26 Aug, 2017 1 commit
  5. 11 May, 2017 1 commit
  6. 11 Apr, 2017 2 commits
    • 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
    • Daniel Pfeifer's avatar
      cmConfigure: Ensure separate include block in headers · 5afac50f
      Daniel Pfeifer authored
      Make sure that `#include <cmConfigure.h>` is followed by an empty line
      in header files.  This is necessary to make sure that changing <> to ""
      does not affect the include ordering of clang-format.
      
      Automate with:
      
      git grep -l '#include <cmConfigure.h>' | grep -v '.cxx$' \
      | xargs sed -i '/#include <cmConfigure.h>/ { N; N; s/\n\{1,2\}/\n\n/ }'
      5afac50f
  7. 24 Oct, 2016 1 commit
  8. 22 Oct, 2016 1 commit
  9. 21 Oct, 2016 1 commit
  10. 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
  11. 27 Jun, 2016 1 commit
  12. 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
  13. 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
  14. 07 Apr, 2014 1 commit
  15. 08 Mar, 2014 1 commit
  16. 16 Oct, 2013 1 commit
    • Brad King's avatar
      Drop builtin command documentation · e33d8d2d
      Brad King authored
      Drop all GetTerseDocumentation and GetFullDocumentation methods from
      commands.  The command documentation is now in Help/command/*.rst files.
      e33d8d2d
  17. 24 Jul, 2013 1 commit
    • Stephen Kelly's avatar
      Remove the LINK_LANGUAGE generator expression. · 4f6bd702
      Stephen Kelly authored
      It accepted an optional argument to test for equality, but no way
      to get the linker language of a particular target.
      
      TARGET_PROPERTY provides this flexibility and STREQUAL provides
      the necessary API for equality test.
      
      Extend the CompileDefinitions test to cover accessing the
      property of another target.
      4f6bd702
  18. 16 Jul, 2013 1 commit
  19. 02 Jul, 2013 1 commit
  20. 24 May, 2013 1 commit
  21. 25 Mar, 2013 1 commit
  22. 31 Jan, 2013 1 commit
    • Brad King's avatar
      Fix use of cmTypeMacro in new command classes · 9397270d
      Brad King authored
      Both commit 8a37ebec (Add the target_include_directories command,
      2013-01-01) and commit fc61a7a7 (Add the target_compile_definitions
      command, 2013-01-08) added command implementations deriving from the new
      cmTargetPropCommandBase class.  Fix cmTypeMacro declarations of the
      inheritance relationship.
      9397270d
  23. 29 Jan, 2013 2 commits
  24. 21 Jan, 2013 1 commit
    • Stephen Kelly's avatar
      Disallow porcelain to populate includes and defines of IMPORTED targets. · b98d14d4
      Stephen Kelly authored
      With similar reasoning to the parent commit, as downstreams, we can't
      determine what $<CONFIG> generator expressions would be appropriate.
      
      Upstream would have populated the INTERFACE_INCLUDE_DIRECTORIES with
      config-specific generator expressions, possibly appropriate for
      their DEBUG_CONFIGURATIONS. In theory, if we would add include
      directories for a DEBUG intent, we would have to match the upstream
      configurations for that.
      
      Rather than attempting to discover the appropriate configurations
      at this time, simplify the feature instead. The use of IMPORTED targets
      with these commands could still be added in the future if targets
      would export their DEBUG_CONFIGURATIONS somehow.
      b98d14d4
  25. 13 Jan, 2013 1 commit
  26. 10 Jan, 2013 1 commit