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.
25483 Commits
6 Branches
127 Tags
3.0 GiB
 
 
 
 
 
 
Tag: Branch: Tree: 682e03bdb2
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '682e03bdb2'
${ noResults }
Go to file
Alexander Alekhin 682e03bdb2
Merge pull request #13877 from LaurentBerger:pythonvideo 		6 years ago
.github migration: github.com/opencv/opencv 9 years ago
3rdparty Merge pull request #13808 from tailsu:sd/libtiff-4.0.10 6 years ago
apps spelling fixes 6 years ago
cmake Merge pull request #13435 from alalek:issue_13434 6 years ago
data Some mist. typo fixes 7 years ago
doc Check return value in python tutorial 6 years ago
include add missing DNN header to opencv2/opencv.hpp 7 years ago
modules Merge pull request #13884 from dkurt:dnn_drop_ie_r1_r2 6 years ago
platforms Add tests for features2d JavaScript bindings 6 years ago
samples Fix arguments parsing. Add possibility to choose between different features type. Add keypoints matching visualization. Auto format code. 6 years ago
.editorconfig add .editorconfig 6 years ago
.gitattributes cmake: generate and install ffmpeg-download.ps1 7 years ago
.gitignore git: .gitignore update 7 years ago
CMakeLists.txt cmake: allow FFmpeg linking on Android 6 years ago
CONTRIBUTING.md migration: github.com/opencv/opencv 9 years ago
LICENSE copyright: 2019 6 years ago
README.md Improve README (#9243) 7 years ago

README.md

OpenCV: Open Source Computer Vision Library

Resources

Contributing

Please read the contribution guidelines before starting work on a pull request.

Summary of the 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.