1. 07 Mar, 2016 1 commit
  2. 17 Sep, 2015 3 commits
  3. 16 Sep, 2015 3 commits
  4. 06 Jul, 2015 1 commit
    • Matt McCormick's avatar
      FindPythonLibs: Find the python.org libraries (#14809) · 02fd0356
      Matt McCormick authored
      Address the test case
      
        cmake_minimum_required(VERSION 2.8)
        set(Python_ADDITIONAL_VERSIONS 3.4 3.5 3.6)
        find_package(PythonLibs 3 REQUIRED)
      
      with a Python 3.4.x .pkg installed from python.org on OSX.
      
      Temporarily set CMAKE_FIND_FRAMEWORK to LAST to avoid finding the
      system Python.h prematurely.
      
      Add directories inside the frameworks to the search list for the library
      as is done for the header.
      02fd0356
  5. 14 Mar, 2014 1 commit
  6. 06 Mar, 2014 1 commit
  7. 05 Mar, 2014 1 commit
    • Brad King's avatar
      FindPythonLibs: Do not try to find the interpreter (#13794) · bf28ff1f
      Brad King authored
      The parent commit taught FindPythonLibs to try to find PythonInterp
      unconditionally.  Some projects may want the libraries of a specific
      version even when the corresponding interpreter is not available.  Drop
      the internal use of FindPythonInterp and just use the versions from it
      if it happens to have been found by the project first.  That will allow
      projects to get a consistent version when they want both but not
      otherwise force them to find the interpreter.
      bf28ff1f
  8. 03 Mar, 2014 1 commit
    • Matt McCormick's avatar
      FindPythonLibs: Find consistent Python interp, headers, libs (#13794) · 3816cd2d
      Matt McCormick authored
      When possible, get consistent version of the Python interpreter, headers path,
      and library.
      
      Now find_package(PythonLibs) internally calls find_package(PythonInterp
      QUIET) and uses the resulting PYTHON_VERSION_MAJOR and
      PYTHON_VERSION_MINOR to prefer these versions when looking for the
      header path and library.  The Python_ADDITIONAL_VERSIONS variable has
      priority over the interpreter version.
      
      Co-Author: Adam Wolf
      Co-Author: Gert Wollny <gw.fossdev@gmail.com>
      3816cd2d
  9. 15 Oct, 2013 1 commit
  10. 31 Aug, 2013 1 commit
  11. 04 Nov, 2012 1 commit
  12. 13 Aug, 2012 2 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
      9db31162
    • 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
      77543bde
  13. 05 Jun, 2012 1 commit
  14. 22 May, 2012 1 commit
  15. 27 Mar, 2012 2 commits
    • Ben Boeckel's avatar
      Search for other ABIFLAGS builds of Python · 4bdec581
      Ben Boeckel authored
      Starting with Python3, standard Python installs may have additional ABI
      flags attached to include directories and library names. As of 3.2, the
      following flags are in the configure file:
      
          d -> --with-debug
          m -> --with-pymalloc
          u -> --with-wide-unicode
      
      Python 3.3 seems to no longer have --with-wide-unicode. Hopefully Python
      will ensure that the possible flags always show up in a stable order.
      The 'd' flag is ignored since the debug library is considered separate.
      
      There is still the problem where ABI flags cannot be specified in
      find_package since the letters confuse the version comparator.
      4bdec581
    • Ben Boeckel's avatar
      Don't put legacy variables back into the cache · 6a46f5ce
      Ben Boeckel authored
      If PYTHON_INCLUDE_PATH is put into the cache, then it will always
      override whatever might be found and PYTHON_INCLUDE_DIR is never given a
      chance to find something different. It being marked as INTERNAL also
      means that it cannot be changed without editing CMakeCache.txt directly.
      
      Basically, the scenario is that if the Python version is changed, then
      deleting PYTHON_INCLUDE_DIR doesn't work because any cached
      PYTHON_INCLUDE_PATH variable is set before find_path is even called. Any
      build tree using a previous version will still need either manual
      removal of PYTHON_INCLUDE_PATH or a complete reconfigure, but in the
      future changing the Python version can be accomplished by deleting
      PYTHON_INCLUDE_DIR and reconfiguring with the new version.
      6a46f5ce
  16. 23 Feb, 2012 2 commits
  17. 22 Feb, 2012 3 commits
  18. 10 Jan, 2012 1 commit
    • Christian Andersson's avatar
      FindPythonLibs: Search for single-user installs on Windows · a04ced3b
      Christian Andersson authored
      When cmake searches for Python libs in Windows it searches in:
      
        [HKEY_LOCAL_MACHINE\\SOFTWARE\\Python\\PythonCore\\${_CURRENT_VERSION}\\InstallPath]/libs
      
      However, the information might not always reside there.  The information
      could also reside in:
      
        [HKEY_CURRENT_USER\\SOFTWARE\\Python\\PythonCore\\${_CURRENT_VERSION}\\InstallPath]/libs
      
      when one installs Python for a single user and not for all users.
      a04ced3b
  19. 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
      
        include(FindPackageHandleStandardArgs)
      
      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.
      c4275592
  20. 17 Jan, 2011 1 commit
  21. 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).
      2d3594b1
  22. 04 Jan, 2011 1 commit
  23. 19 Oct, 2010 1 commit
  24. 28 Sep, 2010 1 commit
  25. 24 Sep, 2010 1 commit
  26. 13 Aug, 2010 1 commit
  27. 09 Aug, 2010 1 commit
  28. 17 Feb, 2010 3 commits
  29. 28 Jan, 2010 1 commit