1. 23 May, 2021 2 commits
  2. 27 Jun, 2020 1 commit
  3. 03 May, 2020 1 commit
    • Pino Toscano's avatar
      cmake: switch python & boost-python search to py3 · 1fdeff25
      Pino Toscano authored
      Python 2 is EOL now, and Python 3 has been available in distros for
      years already, so it is time to switch exclusively to Python 3.
      The actual changes to the BoostPython module are:
      - look for the python3 boost component (instead of python): while boost
        upstream does not provide it, most of the distros do; the alternative
        would be to look for the pythonXY components, which is not ideal...
      - look for the python libraries >= 3, setting as additional versions
        for the cmake module all the non-EOL Python 3 versions
      - set as Python versions for pkg-config all the non-EOL ones, using the
        embed version starting from Python 3.8 [1]
      [1] https://bugs.python.org/issue36721
      BUG: 419237
      FIXED-IN: 20.07.80
  4. 24 Dec, 2018 1 commit
  5. 06 Aug, 2013 1 commit
    • David Narváez's avatar
      Rewrite FindBoostPython.cmake for correctness and stability · 724396ea
      David Narváez authored
      1. Return compile check (see BoostPython_TRY_COMPILE() macro), it's
      needed for some cases. Say, default Python in system is Python 3.3, and
      it gets picked up. But Boost 1.53 python library could not work with it
      and requires Python 2.x. Without compile check you'll pick up
      uncompatible Python version.
      2. find_package(PkgConfig) moved under corresponding if(...) and
      if(PKG_CONFIG_FOUND) is checked after. While it's spread enough, there
      is no guarantee you'll have pkg-config on that system. Also,
      PYTHON_VERSIONS moved closer to the scope where it's used to improve
      3. Use standard CMake find_package_handle_standard_args() and
      cmake_push_check_state()/cmake_pop_check_state() instead of rolling own
      equivalent logic. The latter logic was ever wrong, making
      HAVE_BOOST_SHARED_PTR_HPP check fail.
      4. BoostPython_INCLUDE_DIRS and BoostPython_LIBRARIES are saved in
      cache, as other CMake modules do. This unbreaks the situation when CMake
      detects that it should be re-run (for example, some CMakeLists.txt file
      was modified), and runs through modules again - in this case, if
      BoostPython_INCLUDE_DIRS and BoostPython_LIBRARIES are not in cache, all
      tests will be run again, and probably fail now.
      BUG: 320807
      FIXED-IN: 4.12
      REVIEW: 110954
  6. 05 Aug, 2013 1 commit
    • David Narváez's avatar
      Stylistic changes to FindBoostPython.cmake and framework · a563705e
      David Narváez authored
      Polish FindBoostPython.cmake from CMake's point of view:
       * Use BoostPython_ prefix instead of BOOST_PYTHON_
         (BOOSTPYTHON_ is also acceptable but is unreadable);
       * Remove extra call to find_package(BoostPython);
       * Replace macro_optional_find_package() with simple find_package(),
         CMake has CMAKE_DISABLE_FIND_PACKAGE_Foo feature for a while.
      This is a first patch of a bigger set, containing only minor fixes.
      CCBUG: 320807
      REVIEW: 110953
  7. 02 Apr, 2013 1 commit
  8. 10 Feb, 2012 1 commit
    • Thiago Macieira's avatar
      Improve the finding of libboost-python · 28961e50
      Thiago Macieira authored
      Use pkg-config to find Python if we can, then use find_package(Boost)
      to find the boost-python libs.
      The code below the pkg-config finding inserts -L/usr/lib, which is a
      bad idea.
  9. 05 Jul, 2011 1 commit
  10. 10 Apr, 2011 1 commit
  11. 09 Feb, 2011 1 commit