1. 07 Mar, 2016 1 commit
  2. 16 Sep, 2015 1 commit
  3. 02 Dec, 2014 1 commit
  4. 14 Apr, 2014 1 commit
  5. 14 Mar, 2014 2 commits
  6. 06 Mar, 2014 1 commit
  7. 24 Oct, 2013 1 commit
  8. 15 Oct, 2013 1 commit
  9. 31 Aug, 2013 1 commit
  10. 13 Aug, 2012 1 commit
    • 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
  11. 27 Feb, 2012 1 commit
    • Rolf Eike Beer's avatar
      FindPythonInterp: rework the version detection · 7d6db93d
      Rolf Eike Beer authored
      There are versions out there that neither understand --version nor -V. Try a
      completely different approach: execute a small python script that prints the
      version number (and only that) in an easily reusable way using
      sys.version_info. This is documented to work since Python 2.0. Use sys.version
      for older versions, which is documented to exist since 1.5. If even that
      doesn't work then simply assume we are on 1.4.0.
  12. 22 Feb, 2012 1 commit
  13. 27 Jan, 2012 1 commit
  14. 19 Jan, 2012 1 commit
    • Rolf Eike Beer's avatar
      FindPythonInterp: fix version parsing · aa11536c
      Rolf Eike Beer authored
      On dashmacmini2 the test showed output like this:
      -- Found PythonInterp: /usr/bin/python (found version "Unknown option: --
      usage: /usr/bin/python [option] ... [-c cmd | file | -] [arg] ...
      Try `python -h' for more information.")
      On my machine where python outputs "Python 2.7" this worked, but
      set to "2.7".
      Add some checks that the version output has the expected form before using it.
  15. 18 Jan, 2012 1 commit
    • Rolf Eike Beer's avatar
      FindPythonInterp: make version selectable · 0fe4d69b
      Rolf Eike Beer authored
      This allows the developer to tell FindPythonInterp which Python version should
      be searched for. This allows the right version to be chosen for a project
      without user assistance if there are specific requirements. This is especially
      useful as it is common to have major versions 2 and 3 installed in parallel,
      which are partly incompatible.
  16. 23 Aug, 2011 4 commits
    • Björn Ricks's avatar
      Use FIND_PACKAGE_HANDLE_STANDARD_ARGS second mode · 1c2508a5
      Björn Ricks authored
      Using the second mode of FIND_PACKAGE_HANDLE_STANDARD_ARGS allows for
      checking the version number. Now a user can require a minimum version of
      the python interpreter with find_package(PythonInterp VERSION)
    • Björn Ricks's avatar
      Update documentation of FindPythonInterp.cmake · d1795002
      Björn Ricks authored
      Document new variables and update also comments in cmake code to explain
      the current behaviour of FindPythonInterp.cmake module
    • Björn Ricks's avatar
      Determine python version · 4fd1e284
      Björn Ricks authored
    • Björn Ricks's avatar
      Search for the installed python interpreter first · 20980ef5
      Björn Ricks authored
      The old approach to determine the python executeable chooses the newest
      version from _Python_VERSIONS if no additonal versions are passed.
      With python it is possible to install different versions side-by-side.
      Therefore a user can install e.g. python 2.5 and 2.7. Python 2.7 maybe
      only installed for testing new features and 2.5 for building and running
      his software. Thus the default installation for the user would be python
      2.5 and then returning PYTHON_EXECUTEABLE python2.7 would be wrong. The
      new approuch searches first for the the default python executable e.g.
      /usr/bin/python on unix and if it can't be found _Python_VERSIONS is
  17. 20 Jan, 2011 1 commit
    • Brad King's avatar
      Modules: Include builtin FindPackageHandleStandardArgs directly · c4275592
      Brad King authored
      The FindPackageHandleStandardArgs module was originally created outside
      of CMake.  It was added for CMake 2.6.0 by commit e118a627 (add a macro
      FIND_PACKAGE_HANDLE_STANDARD_ARGS..., 2007-07-18).  However, it also
      proliferated into a number of other projects that at the time required
      only CMake 2.4 and thus could not depend on CMake to provide the module.
      CMake's own find modules started using the module in commit b5f656e0
      (use the new FIND_PACKAGE_HANDLE_STANDARD_ARGS in some of the FindXXX
      modules..., 2007-07-18).
      Then commit d358cf5c (add 2nd, more powerful mode to
      find_package_handle_standard_args, 2010-07-29) added a new feature to
      the interface of the module that was fully optional and backward
      compatible with all existing users of the module.  Later commit 5f183caa
      (FindZLIB: use the FPHSA version mode, 2010-08-04) and others shortly
      thereafter started using the new interface in CMake's own find modules.
      This change was also backward compatible because it was only an
      implementation detail within each module.
      Unforutnately these changes introduced a problem for projects that still
      have an old copy of FindPackageHandleStandardArgs in CMAKE_MODULE_PATH.
      When any such project uses one of CMake's builtin find modules the line
      loads the copy from the project which does not have the new interface!
      Then the including find module tries to use the new interface with the
      old module and fails.
      Whether this breakage can be considered a backward incompatible change
      in CMake is debatable.  The situation is analagous to copying a standard
      library header from one version of a compiler into a project and then
      observing problems when the next version of the compiler reports errors
      in its other headers that depend on its new version of the original
      header.  Nevertheless it is a change to CMake that causes problems for
      projects that worked with previous versions.
      This problem was discovered during the 2.8.3 release candidate cycle.
      It is an instance of a more general problem with projects that provide
      their own versions of CMake modules when other CMake modules depend on
      them.  At the time we resolved this instance of the problem with commit
      b0118402 (Use absolute path to FindPackageHandleStandardArgs.cmake
      everywhere, 2010-09-28) for the 2.8.3 release.
      In order to address the more general problem we introduced policy
      CMP0017 in commit db44848f (Prefer files from CMAKE_ROOT when including
      from CMAKE_ROOT, 2010-11-17).  That change was followed by commit
      ce28737c (Remove usage of CMAKE_CURRENT_LIST_DIR now that we have
      CMP0017, 2010-12-20) which reverted the original workaround in favor of
      using the policy.  However, existing project releases do not set the
      policy behavior to NEW and therefore still exhibit the problem.
      We introduced in commit a364daf1 (Allow users to specify defaults for
      unset policies, 2011-01-03) an option for users to build existing
      projects by adding -DCMAKE_POLICY_DEFAULT_CMP0017=NEW to the command
      line.  Unfortunately this solution still does not allow such projects to
      build out of the box, and there is no good way to suggest the use of the
      new option.
      The only remaining solution to keep existing projects that exhibit this
      problem building is to restore the change originally made in commit
      b0118402 (Use absolute path to FindPackageHandleStandardArgs.cmake
      everywhere, 2010-09-28).  This also avoids policy CMP0017 warnings for
      this particular instance of the problem the policy addresses.
  18. 10 Jan, 2011 1 commit
    • Marcus D. Hanwell's avatar
      Python additional version support, bug #10279. · 2d3594b1
      Marcus D. Hanwell authored
      Introduced an additional variable, Python_ADDITIONAL_VERSIONS, to both
      FindPythonLibs and FindPythonInterp. Changed FindPythonInterp to loop
      over versions rather than hardcoding all versions (more like libs).
  19. 04 Jan, 2011 1 commit
  20. 28 Sep, 2010 1 commit
  21. 21 Sep, 2010 1 commit
  22. 09 Aug, 2010 1 commit
  23. 01 Oct, 2009 1 commit
  24. 28 Sep, 2009 1 commit
    • Brad King's avatar
      Convert CMake find-modules to BSD License · c4bb9c9d
      Brad King authored
      This adds copyright/license notification blocks CMake's find-modules.
      Many of the modules had no notices at all.  Some had notices referring
      to the BSD license already.  This commit normalizes existing notices and
      adds missing notices.
  25. 10 Jan, 2009 1 commit
  26. 30 Aug, 2007 1 commit
    • Alexander Neundorf's avatar
      · 52bf51b4
      Alexander Neundorf authored
      ENH: add support for the next python release, python 2.6
  27. 23 Jul, 2007 2 commits
    • Alexander Neundorf's avatar
      · 3c92cfbe
      Alexander Neundorf authored
      STYLE: mark the variable as advanced
    • Alexander Neundorf's avatar
      · 13db5b57
      Alexander Neundorf authored
      ENH: add second failure message parameter to
      FIND_PACKAGE_HANDLE_STANDARD_ARGS(), so cmake modules can specify their own
      better failure messages. If the default is ok use "DEFAULT_MSG".
      Do this also for FindBoost.cmake (#5349)
  28. 18 Jul, 2007 1 commit
    • Alexander Neundorf's avatar
      · b5f656e0
      Alexander Neundorf authored
      ENH: use the new FIND_PACKAGE_HANDLE_STANDARD_ARGS in some of the FindXXX
      modules, remove some of the extra search paths which are also searched by
  29. 27 Sep, 2006 1 commit
    • Alexander Neundorf's avatar
      · 5d22d36c
      Alexander Neundorf authored
      ENH: apply patch from Dirk Mueller to support Python 2.5
  30. 15 Dec, 2005 1 commit
  31. 14 Dec, 2005 1 commit
  32. 15 Jul, 2005 3 commits