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.
16507 Commits
7 Branches
126 Tags
3.0 GiB
 
 
 
 
 
 
Tag: Branch: Tree: 56e637d5f4
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '56e637d5f4'
${ noResults }
Go to file
Vadim Pisarevsky 56e637d5f4
Merge pull request #4135 from lupustr3:ipp_code_refactoring 		10 years ago
3rdparty AndroidMgr: fixed package build 10 years ago
apps fixed vector out of range exception in nextImg 10 years ago
cmake Android: renamed default library name for static and dynamic fallback load; fixed libz import for 64-bit platforms 10 years ago
data move data/detect_blob.png in samples/data 10 years ago
doc Updated Manager for Android 10 years ago
include Added cmake option for abi descriptor generating (GENERATE_ABI_DESCRIPTOR) 10 years ago
modules Merge pull request #4135 from lupustr3:ipp_code_refactoring 10 years ago
platforms Updated android manager readme file 10 years ago
samples move data/detect_blob.png in samples/data 10 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 fix support for pthreads parallel_for 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.