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.
19651 Commits
6 Branches
128 Tags
3.0 GiB
 
 
 
 
 
 
Tag: Branch: Tree: 30a6cee2fe
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '30a6cee2fe'
${ noResults }
Go to file
Pavel Vlasov 30a6cee2fe
Instrumentation for OpenCV API regions and IPP functions; 		9 years ago
.github migration: github.com/opencv/opencv 9 years ago
3rdparty Merge pull request #6899 from alalek:ffmpeg_update 9 years ago
apps Fix build interactive-calibration app 9 years ago
cmake Merge pull request #7101 from lupustr3:pvlasov/instrumentation 9 years ago
data Removing whitespace to appease doc builder 9 years ago
doc Merge pull request #6945 from sturkmen72:update_documentation 9 years ago
include fix inclusion of OpenCV header opencv.hpp 9 years ago
modules Instrumentation for OpenCV API regions and IPP functions; 9 years ago
platforms ios: reduce number of test configurations in precommit builds 9 years ago
samples Merge pull request #6945 from sturkmen72:update_documentation 9 years ago
.gitattributes Made changes to OpenCVFindMatlab suggested by SpecLad 12 years ago
.gitignore Improved thrust interop tutorial. 10 years ago
.tgitconfig Add tgit.icon project config 11 years ago
CMakeLists.txt Implementations instrumentation framework for OpenCV performance system; 9 years ago
CONTRIBUTING.md migration: github.com/opencv/opencv 9 years ago
LICENSE Update license year range to 2016 9 years ago
README.md migration: github.com/opencv/opencv 9 years ago

README.md

OpenCV: Open Source Computer Vision Library

Resources

Contributing

Please read before starting work on a pull request: https://github.com/opencv/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.