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.
15123 Commits
7 Branches
126 Tags
3.0 GiB
 
 
 
 
 
 
Tag: Branch: Tree: 1f43999f2a
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '1f43999f2a'
${ noResults }
Go to file
Vadim Pisarevsky 1f43999f2a
Merge pull request #3428 from 23pointsNorth:patch-6 		10 years ago
3rdparty update IPPICV package 10 years ago
apps Several type of formal refactoring: 10 years ago
cmake Remove redundant -mfpu=neon flag. 10 years ago
data moved part of video to contrib/{outflow, bgsegm}; moved matlab to contrib 10 years ago
doc Merge pull request #3426 from mshabunin:doxygen-imgproc 10 years ago
include Split highgui module to videoio and highgui 10 years ago
modules Merge pull request #3428 from 23pointsNorth:patch-6 10 years ago
platforms Fixing iOS clang warnings, part 3 10 years ago
samples fix gpu sample performance test cpu part 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 silence cmake 3.0+ warnings on LOCATION attribute 10 years ago
LICENSE adding LICENSE file and a sample of its reference in ocl.hpp 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.