mirror/opencv
1
0
Fork 0
mirror of https://github.com/opencv/opencv.git synced 2024-11-25 03:30:34 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
Open Source Computer Vision Library
13,749 Commits 6 Branches 126 Tags 3 GiB
C++ 87%
C 3.4%
Python 2.8%
CMake 2.1%
Java 1.6%
Other 2.9%
47e345bcb6
Go to file
Fco. Javier Delgado del Hoyo 47e345bcb6 Change comment according to fix
2014-06-25 11:49:26 +02:00
3rdparty icv: enable public IPPICV packages 2014-05-23 13:43:31 +04:00
apps Merge remote-tracking branch 'origin/2.4' into merge-2.4 2014-01-27 15:28:14 +04:00
cmake android: allow to build & run examples without Android OpenCV Manager 2014-06-06 18:01:04 +04:00
data Merge pull request #2828 from otsedom:updating_and_adding_haarcascades_mcs 2014-06-12 21:39:50 +04:00
doc Updates python feature matching tutorial 2014-06-24 11:35:22 +02:00
include Merge remote-tracking branch 'origin/2.4' into merge-2.4 2014-01-27 15:28:14 +04:00
modules Change comment according to fix 2014-06-25 11:49:26 +02:00
platforms Merge remote-tracking branch 'origin/2.4' into merge-2.4 2014-05-12 17:38:07 +04:00
samples Update MatchTemplate_Demo.cpp 2014-06-11 10:29:30 +02: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 Don't build CUDA modules stubs by default (use -DBUILD_CUDA_STUBS=ON if need them) 2014-06-16 11:18:52 +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

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.