Chiebot-Mirror
/
opencv
mirror of https://github.com/opencv/opencv.git
8
0
Fork 0
Code Issues Projects Releases Wiki Activity
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.
13848 Commits
6 Branches
126 Tags
3.0 GiB
 
 
 
 
 
 
Tag: Branch: Tree: d58f736935
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'd58f736935'
${ noResults }
Go to file
vbystricky d58f736935
Split highgui module to videoio and highgui 		11 years ago
3rdparty Extract imgcodecs module from highgui 11 years ago
apps Extract imgcodecs module from highgui 11 years ago
cmake Split highgui module to videoio and highgui 11 years ago
data Merge pull request #2828 from otsedom:updating_and_adding_haarcascades_mcs 11 years ago
doc Split highgui module to videoio and highgui 11 years ago
include Split highgui module to videoio and highgui 11 years ago
modules Split highgui module to videoio and highgui 11 years ago
platforms Merge remote-tracking branch 'origin/2.4' into merge-2.4 11 years ago
samples Split highgui module to videoio and highgui 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 Split highgui module to videoio and highgui 11 years ago
LICENSE Initial Linux packages build rools for CPack. 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.