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.
14111 Commits
7 Branches
126 Tags
3.0 GiB
 
 
 
 
 
 
Tag: Branch: Tree: 2353436cb5
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '2353436cb5'
${ noResults }
Go to file
edgarriba 2353436cb5
Removed whitespace 		10 years ago
3rdparty Merge pull request #2925 from BloodAxe:osx-framework-script 10 years ago
apps made everything compile and even run somehow 10 years ago
cmake Another typo in comment inside OpenNI2 cmake file 10 years ago
data Merge pull request #2828 from otsedom:updating_and_adding_haarcascades_mcs 11 years ago
doc Removed whitespace 10 years ago
include Split highgui module to videoio and highgui 10 years ago
modules Merge remote-tracking branch 'upstream/master' 10 years ago
platforms Fix cmake to build OpenCV framework on OSX 11 years ago
samples Tutorial code restructure 10 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 Merge remote-tracking branch 'origin/master' into Openni2Support 10 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.