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.
15144 Commits
7 Branches
126 Tags
3.0 GiB
 
 
 
 
 
 
Tag: Branch: Tree: a1e04c98aa
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'a1e04c98aa'
${ noResults }
Go to file
TobyWanKenobi a1e04c98aa
Add method in StatModel class, to load from String 		10 years ago
3rdparty update IPPICV package 10 years ago
apps Several type of formal refactoring: 10 years ago
cmake Remove redundant -mfpu=neon flag. 10 years ago
data moved part of video to contrib/{outflow, bgsegm}; moved matlab to contrib 10 years ago
doc Doxygen documentation: BiB references and fixes 10 years ago
include Split highgui module to videoio and highgui 10 years ago
modules Add method in StatModel class, to load from String 10 years ago
platforms Fixing iOS clang warnings, part 3 10 years ago
samples Merge pull request #3463 from Dikay900:fix_sample_video_writer 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 silence cmake 3.0+ warnings on LOCATION attribute 10 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.