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.
18291 Commits
7 Branches
128 Tags
3.0 GiB
 
 
 
 
 
 
Tag: Branch: Tree: 9c0a5523e4
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '9c0a5523e4'
${ noResults }
Go to file
Vadim Pisarevsky 9c0a5523e4
Merge pull request #5757 from alalek:merge-2.4 		9 years ago
3rdparty Merge 2.4 into master 9 years ago
apps Merge pull request #5757 from alalek:merge-2.4 9 years ago
cmake Merge pull request #5757 from alalek:merge-2.4 9 years ago
data move data/detect_blob.png in samples/data 10 years ago
doc Merge pull request #5633 from mshabunin:doc-mser 9 years ago
include Added cmake option for abi descriptor generating (GENERATE_ABI_DESCRIPTOR) 10 years ago
modules Merge pull request #5757 from alalek:merge-2.4 9 years ago
platforms New variant of iOS framework building, fixed some warnings for XCode 7.1.1 and cmake 3.3.2 9 years ago
samples Merge 2.4 into master 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 Merge pull request #5757 from alalek:merge-2.4 9 years ago
CONTRIBUTING.md add link to contributing guidelines 10 years ago
LICENSE 1. Input/OutputArray optimizations; 10 years ago
README.md Update README.md 10 years ago

README.md

OpenCV: Open Source Computer Vision Library

Gittip

Resources

Contributing

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