Open Source Computer Vision Library https://opencv.org/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Ernest Galbrun 062e1cbe06 edited documentation to take into account changes in TVL1 11 years ago
3rdparty icv: enable public IPPICV packages 11 years ago
apps removed contrib, legacy and softcsscade modules; removed latentsvm and datamatrix detector from objdetect. removed haartraining and sft apps. 11 years ago
cmake android: allow to build & run examples without Android OpenCV Manager 11 years ago
data Merge pull request #2828 from otsedom:updating_and_adding_haarcascades_mcs 11 years ago
doc Updates python feature matching tutorial 11 years ago
include removed contrib, legacy and softcsscade modules; removed latentsvm and datamatrix detector from objdetect. removed haartraining and sft apps. 11 years ago
modules edited documentation to take into account changes in TVL1 11 years ago
platforms Merge remote-tracking branch 'origin/2.4' into merge-2.4 11 years ago
samples Merge pull request #2626 from KayKwon:matlab_formatter 11 years ago
.gitattributes Made changes to OpenCVFindMatlab suggested by SpecLad 11 years ago
.gitignore Merge remote-tracking branch 'origin/2.4' into merge-2.4 11 years ago
.tgitconfig Add tgit.icon project config 11 years ago
CMakeLists.txt Don't build CUDA modules stubs by default (use `-DBUILD_CUDA_STUBS=ON` if need them) 11 years ago
LICENSE adding LICENSE file and a sample of its reference in ocl.hpp 11 years ago
README.md Replaced Gittip button 11 years ago
index.rst GSoC Python Tutorials 11 years ago

README.md

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.