1. 12 Jan, 2017 1 commit
    • Konstantin Podsvirov's avatar
      QtIFW: Improved packaging · 49717993
      Konstantin Podsvirov authored
      Now cpack_ifw_configure_file command used to configure
      template files of component's scripts.
      Now for these template files we can use QtIFW predefined
      variables (like @VAR@) and template variables
      in Qt/IFW/SDK/Creator templates style (like %VAR%).
      Now CMake_INSTALL_INFIX advanced variable used to configure
      CMake installation destination when package as part of QtSDK.
  2. 30 Nov, 2016 1 commit
  3. 09 Oct, 2016 1 commit
    • Daniel Pfeifer's avatar
      CMakeCPack: remove obsolete conditions · 66c6144c
      Daniel Pfeifer authored
      The file contains some conditions depending on the existence of CMake
      modules.  This basically checks for CMake versions that are no longer
      supported.  Remove the conditions.
  4. 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.
  5. 12 Sep, 2016 1 commit
  6. 16 Aug, 2016 1 commit
  7. 13 Jul, 2016 2 commits
  8. 17 Jun, 2016 1 commit
  9. 01 Jun, 2016 1 commit
  10. 09 Feb, 2016 1 commit
  11. 27 Jul, 2015 1 commit
  12. 07 Jul, 2015 5 commits
  13. 11 Sep, 2014 1 commit
  14. 12 Aug, 2014 1 commit
    • Konstantin Podsvirov's avatar
      CPackIFW: Revise this generator · e6496b60
      Konstantin Podsvirov authored
      CPack IFW generator updates:
      - Group now can have script;
      - Root package (for monolithic or one package installers) can be
        configured from group.
      CMake updates:
      - Native installation (no Unspecified component).
  15. 29 Jul, 2014 1 commit
  16. 28 Jul, 2014 1 commit
  17. 12 Nov, 2013 1 commit
    • Brad King's avatar
      Configure NSIS-packaged CMake version and install destination · 84af42b9
      Brad King authored
      Remove the version number from the default package install destination.
      An unversioned default allows users to upgrade their CMake installations
      without manually re-generating all their build trees to update the path
      to CMake.  Users can select a versioned directory name on installation
      if they wish.
      Also name the package with the full CMake version number so it is clear
      exactly what version is going to be installed.  This is particularly
      helpful for the nightly binary installers.
  18. 19 Jul, 2013 1 commit
    • Richard's avatar
      CMakeCPack: Provide an upgrade guid for WiX · 155bb01b
      Richard authored
      Set CPACK_WIX_UPGRADE_GUID.  Without this upgrade GUID, you end up with
      multiple instances of the same installation when installing cmake from a
      WIX generated installer.
  19. 16 Aug, 2012 1 commit
  20. 13 Aug, 2012 3 commits
    • Kitware Robot's avatar
      Remove CMake-language block-end command arguments · 9db31162
      Kitware Robot authored
      Ancient versions of CMake required else(), endif(), and similar block
      termination commands to have arguments matching the command starting the
      block.  This is no longer the preferred style.
      Run the following shell code:
      for c in else endif endforeach endfunction endmacro endwhile; do
          echo 's/\b'"$c"'\(\s*\)(.\+)/'"$c"'\1()/'
      done >convert.sed &&
      git ls-files -z -- bootstrap '*.cmake' '*.cmake.in' '*CMakeLists.txt' |
      egrep -z -v '^(Utilities/cm|Source/kwsys/)' |
      egrep -z -v 'Tests/CMakeTests/While-Endwhile-' |
      xargs -0 sed -i -f convert.sed &&
      rm convert.sed
    • Kitware Robot's avatar
      Convert CMake-language commands to lower case · 77543bde
      Kitware Robot authored
      Ancient CMake versions required upper-case commands.  Later command
      names became case-insensitive.  Now the preferred style is lower-case.
      Run the following shell code:
      cmake --help-command-list |
      grep -v "cmake version" |
      while read c; do
          echo 's/\b'"$(echo $c | tr '[:lower:]' '[:upper:]')"'\(\s*\)(/'"$c"'\1(/g'
      done >convert.sed &&
      git ls-files -z -- bootstrap '*.cmake' '*.cmake.in' '*CMakeLists.txt' |
      egrep -z -v '^(Utilities/cm|Source/kwsys/)' |
      xargs -0 sed -i -f convert.sed &&
      rm convert.sed
    • Kitware Robot's avatar
      Remove trailing whitespace from most CMake and C/C++ code · 7bbaa428
      Kitware Robot authored
      Our Git commit hooks disallow modification or addition of lines with
      trailing whitespace.  Wipe out all remnants of trailing whitespace
      everywhere except third-party code.
      Run the following shell code:
      git ls-files -z -- \
       bootstrap doxygen.config '*.readme' \
       '*.c' '*.cmake' '*.cpp' '*.cxx' \
       '*.el' '*.f' '*.f90' '*.h' '*.in' '*.in.l' '*.java' \
       '*.mm' '*.pike' '*.py' '*.txt' '*.vim' |
      egrep -z -v '^(Utilities/cm|Source/(kwsys|CursesDialog/form)/)' |
      egrep -z -v '^(Modules/CPack\..*\.in)' |
      xargs -0 sed -i 's/ \+$//'
  21. 13 Jan, 2011 2 commits
    • David Cole's avatar
      Add CPACK_NSIS_INSTALL_ROOT for CMake's own installer (#9148) · 96cd1638
      David Cole authored
      Problem with CMake 2.8.4-rc1: when you launch the NSIS exe installer
      on Windows, the default install path shown to the end user is, at first,
      "\CMake 2.8".
      This problem started occurring when configuring CMake itself with an
      older CMake, after adding CPACK_NSIS_INSTALL_ROOT to fix issue 9148.
      So... it's a regression from 2.8.3.
      I forgot (again) that when you add a new CPack variable, you must
      add it to CMake's CMakeCPack.cmake file or else it is empty when
      configured with an older CMake. And on Windows, without a bootstrap
      build available, the releases are always configured with an older
      version of CMake. This may be the last time this has bitten me,
      though, because it is now burned into my brain that problems with
      CMake's installer itself are inevitably associated with adding new
      CPack variables.
      In addition to adding a definition for CPACK_NSIS_INSTALL_ROOT,
      I've gone ahead and made it differ for the 32- and 64-bit builds
      of CMake to give the end user the expected default value for the
      Program Files folder for each one.
      And, since I was adding a new 32/64 differentiator anyhow, I made
      the "NSIS package name" and "installer registry key base" different
      for 64-bit builds, too, by appending " (Win64)" to each one.
      These address the concerns mentioned in 9148's related issue:
      http://public.kitware.com/Bug/view.php?id=9094 (at least as far
      as CMake's installer is concerned). 9094 could still use a good
      general fix for all projects, though, and remains open for now.
    • David Cole's avatar
      David Cole authored
      The parent commit added a warning message whenever a required file
      does not exist.
      As it turns out, the "required" files never exist when built with
      Visual Studio Express editions. Add a variable to suppress these
      warning messages because only packagers or naive includers of
      this file will care to see such warning messages.
      We want to warn about this condition by default so that people who
      are using InstallRequiredSystemLibraries without understanding it
      fully will have a chance of understanding why it's not working in
      the event of missing required files.
      But we also want to give projects the ability to suppress this warning
      (by "project's choice default") so that they can encourage users who
      are restricted to using an Express edition to build their project.
      Packagers should explicitly use...
      ...when building releases. That way, their release build process will warn
      them about any missing files, but only if their project CMakeLists files
      use a construct similar to CMake's:
  22. 09 Jun, 2010 1 commit
    • Brad King's avatar
      Fix CMake data and doc paths in Cygwin package · 6ba45fa9
      Brad King authored
      Override CMAKE_DOC_DIR and CMAKE_DATA_DIR cache entries on Cygwin early
      enough so the new values are used everywhere.  Previously only some of
      the uses were overridden.  Also set CPACK_PACKAGE_VERSION to the whole
      CMake_VERSION so that the Cygwin MANIFEST file goes in the proper path.
  23. 04 May, 2010 1 commit
  24. 01 Oct, 2009 1 commit
  25. 28 Sep, 2009 2 commits
  26. 05 Mar, 2009 1 commit
    • Brad King's avatar
      ENH: Overhaul CMake version numbering · 98c51ff6
      Brad King authored
      This moves the version numbers into an isolated configured header so
      that not all of CMake needs to rebuild when the version changes.
      Previously we had spaces, dashes and/or the word 'patch' randomly chosen
      before the patch number.  Now we always report version numbers in the
      traditional format "<major>.<minor>.<patch>[-rc<rc>]".
      We still use odd minor numbers for development versions.  Now we also
      use the CCYYMMDD date as the patch number of development versions, thus
      allowing tests for exact CMake versions.
  27. 23 May, 2008 1 commit
  28. 20 May, 2008 1 commit
  29. 09 Feb, 2008 1 commit
  30. 07 Nov, 2007 1 commit
  31. 31 Oct, 2007 1 commit