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.
16963 Commits
6 Branches
127 Tags
3.0 GiB
 
 
 
 
 
 
Tag: Branch: Tree: f4c9bc8bc4
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'f4c9bc8bc4'
${ noResults }
Go to file
Alexander Alekhin f4c9bc8bc4
Merge pull request #5406 from cbalint13:master 		9 years ago
3rdparty proposed change by psyill 9 years ago
apps add checks for valid input data given to parameters 9 years ago
cmake Merge pull request #5363 from avershov:opencl-vaapi-detect 9 years ago
data move data/detect_blob.png in samples/data 10 years ago
doc Merge pull request #5295 from LorenaGdL:ml-svm_tutorials 9 years ago
include Added cmake option for abi descriptor generating (GENERATE_ABI_DESCRIPTOR) 10 years ago
modules Speedup AGAST nonmax-suppression. 9 years ago
platforms fixup! Some changes to support mingw-w64 9 years ago
samples Merge pull request #5393 from enesates:patch-1 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 Merge pull request #5272 from avershov:opencl-vaapi-fallback 9 years ago
CONTRIBUTING.md add link to contributing guidelines 9 years ago
LICENSE 1. Input/OutputArray optimizations; 10 years ago
README.md Update README.md 9 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.