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.
16612 Commits
7 Branches
126 Tags
3.0 GiB
 
 
 
 
 
 
Tag: Branch: Tree: e26b941e66
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'e26b941e66'
${ noResults }
Go to file
Vadim Pisarevsky e26b941e66
Merge pull request #4207 from alalek:fix_calib3d_test 		9 years ago
3rdparty update ffmpeg wrapper binaries 10 years ago
apps fixed vector out of range exception in nextImg 10 years ago
cmake fix wrong usage of status(), remove useless message in videoio 9 years ago
data move data/detect_blob.png in samples/data 10 years ago
doc Fixed gen_pattern.py file permission back to 755 10 years ago
include Added cmake option for abi descriptor generating (GENERATE_ABI_DESCRIPTOR) 10 years ago
modules Merge pull request #4207 from alalek:fix_calib3d_test 9 years ago
platforms Adding test support for WINRT 10 years ago
samples simplified sample's interface (remove odd "no processing" branch, add print to screen for processing mode) 9 years ago
.gitattributes Made changes to OpenCVFindMatlab suggested by SpecLad 11 years ago
.gitignore Added support for 'imgcodecs' module: 10 years ago
.tgitconfig Add tgit.icon project config 11 years ago
CMakeLists.txt Adding test support for WINRT 10 years ago
LICENSE 1. Input/OutputArray optimizations; 10 years ago
README.md Replaced Gittip button 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.