Open Source Computer Vision Library
Go to file
Michael Pratt 7d41ce23a7 Build Python 3 bindings in subdirectory
Build the Python 3 cv2 module in lib/python3/, to avoid potential naming
conflicts with the Python 2 bindings.

The Python 2 bindings are placed directly in lib/, where they are
required for the Buildbot to successfully execute the Python tests.
2014-08-07 00:21:42 -04:00
3rdparty Merge pull request #2925 from BloodAxe:osx-framework-script 2014-07-19 18:04:15 +00:00
apps made everything compile and even run somehow 2014-08-03 01:41:09 +04:00
cmake Merge branch 'master' into python2and3 2014-07-31 01:13:16 -04:00
data Merge pull request #2828 from otsedom:updating_and_adding_haarcascades_mcs 2014-06-12 21:39:50 +04:00
doc Merge branch 'master' into python2and3 2014-07-31 01:13:16 -04:00
include Split highgui module to videoio and highgui 2014-07-14 23:16:47 +04:00
modules Build Python 3 bindings in subdirectory 2014-08-07 00:21:42 -04:00
platforms Fix cmake to build OpenCV framework on OSX 2014-07-01 22:31:57 +03:00
samples Merge pull request #3032 from vpisarev:refactor_ml2 2014-08-04 14:51:38 +00:00
.gitattributes Made changes to OpenCVFindMatlab suggested by SpecLad 2013-09-14 13:32:15 +10:00
.gitignore Merge remote-tracking branch 'origin/2.4' into merge-2.4 2014-01-14 11:53:59 +04:00
.tgitconfig Add tgit.icon project config 2014-02-26 17:46:52 +08:00
CMakeLists.txt Merge branch 'master' into python2and3 2014-07-31 01:13:16 -04:00
index.rst GSoC Python Tutorials 2013-09-23 13:41:14 +05:30
LICENSE adding LICENSE file and a sample of its reference in ocl.hpp 2013-12-18 19:33:25 +04:00
README.md Replaced Gittip button 2014-02-15 13:10:09 +04:00

OpenCV: Open Source Computer Vision Library

Gittip

Resources

Contributing

Please read before starting work on a pull request: http://code.opencv.org/projects/opencv/wiki/How_to_contribute

Summary of guidelines:

  • One pull request per issue;
  • Choose the right base branch;
  • Include tests and documentation;
  • Clean up "oops" commits before submitting;
  • Follow the coding style guide.