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.
14851 Commits
7 Branches
126 Tags
3.0 GiB
 
 
 
 
 
 
Tag: Branch: Tree: 18ef0cfe81
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '18ef0cfe81'
${ noResults }
Go to file
Vadim Pisarevsky 18ef0cfe81
Merge pull request #3335 from ilya-lavrenov:neon_ios 		10 years ago
3rdparty Merge pull request #2925 from BloodAxe:osx-framework-script 10 years ago
apps Several type of formal refactoring: 10 years ago
cmake Merge pull request #3216 from xantares:patch-1 10 years ago
data moved part of video to contrib/{outflow, bgsegm}; moved matlab to contrib 10 years ago
doc Merge pull request #3302 from berak:doc_fix_constants_30 10 years ago
include Split highgui module to videoio and highgui 10 years ago
modules this is trivial change; the main change is in opencv_extra - added regression data for perf tests 10 years ago
platforms ability to compile for iOS with Neon 10 years ago
samples Merge pull request #3245 from avdmitry:hello_opencv_sample 10 years ago
.gitattributes Made changes to OpenCVFindMatlab suggested by SpecLad 11 years ago
.gitignore Merge remote-tracking branch 'origin/2.4' into merge-2.4 11 years ago
.tgitconfig Add tgit.icon project config 11 years ago
CMakeLists.txt Merge pull request #3335 from ilya-lavrenov:neon_ios 10 years ago
LICENSE Initial Linux packages build rools for CPack. 11 years ago
README.md Replaced Gittip button 11 years ago
index.rst GSoC Python Tutorials 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.