1. 27 Mar, 2018 1 commit
  2. 09 Feb, 2018 1 commit
  3. 09 Dec, 2017 1 commit
  4. 07 Dec, 2017 1 commit
  5. 15 Nov, 2017 1 commit
  6. 06 Sep, 2017 1 commit
  7. 22 Aug, 2017 1 commit
  8. 19 Aug, 2017 1 commit
  9. 30 Jun, 2017 1 commit
  10. 26 Jun, 2017 1 commit
  11. 10 Nov, 2016 1 commit
  12. 07 Oct, 2016 1 commit
  13. 16 Aug, 2016 1 commit
  14. 13 Jul, 2016 1 commit
  15. 07 Jul, 2016 1 commit
  16. 26 Feb, 2016 1 commit
  17. 17 Dec, 2015 1 commit
  18. 14 Dec, 2015 1 commit
  19. 09 Jun, 2015 1 commit
  20. 24 Mar, 2015 1 commit
    • Tim D. Smith's avatar
      Don't explicitly link Python on OS X · b9b743bb
      Tim D. Smith authored
      Explicitly linking to a Python framework on OS X prevents modules from
      being built against one Python (i.e. system python) and imported from
      another (i.e. Homebrew python); the interpreter segfaults if there's a
      linkage to a foreign Python. Building the module with `-undefined
      dynamic_lookup` instead of an explicit link allows the symbols to be
      resolved at load time from a compatible python.
      b9b743bb
  21. 02 Mar, 2015 1 commit
  22. 18 Feb, 2015 1 commit
  23. 10 Feb, 2015 1 commit
  24. 22 Sep, 2014 1 commit
  25. 01 Sep, 2014 1 commit
  26. 21 Aug, 2014 2 commits
  27. 19 Aug, 2014 4 commits
  28. 15 Aug, 2014 1 commit
  29. 14 Aug, 2014 1 commit
  30. 11 Aug, 2014 1 commit
  31. 10 Aug, 2014 1 commit
  32. 09 Aug, 2014 1 commit
  33. 07 Aug, 2014 2 commits
  34. 06 Aug, 2014 1 commit
    • Michael Pratt's avatar
      Place Python library out in dedicated folder · 9d941155
      Michael Pratt authored
      Place the built Python module library in a dedicated folder inside of
      lib/.  This ensures that even if the Python 2 and Python 3 module names
      conflict, they will not overwrite one another.
      9d941155
  35. 30 Jun, 2014 1 commit
    • Michael Pratt's avatar
      Build both Python 2 and Python 3 bindings · cac1218e
      Michael Pratt authored
      If both Python 2 and Python 3 are found, then build bindings for both of
      them during the build process.  Currently, one version of Python is
      detected automatically, and building for the other requires changes the
      CMake config.
      
      The largest chunk of this change generalizes OpenCVDetectPython.cmake to
      find both a Python 2 and Python 3 version of Python.  Secondly, the
      opencv_python module is split into two modules, opencv_python2 and
      opencv_python3.  Both are built from the same source. but for different
      versions of Python.
      cac1218e