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.
22483 Commits
6 Branches
128 Tags
3.0 GiB
 
 
 
 
 
 
Tag: Branch: Tree: 712689e81a
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '712689e81a'
${ noResults }
Go to file
Vadim Pisarevsky 712689e81a
Merge pull request #9865 from ryanfox:patch-4 		7 years ago
.github migration: github.com/opencv/opencv 9 years ago
3rdparty Updated TBB package to 2018.1 7 years ago
apps Edit spelling mistake in my previous pull request 7 years ago
cmake Merge pull request #9886 from mshabunin:remove-cmake-submodules 7 years ago
data fixing models to resolve XML violation issue 8 years ago
doc Merge pull request #9865 from ryanfox:patch-4 7 years ago
include Merge pull request #7370 from souch55:Fixxn 9 years ago
modules Merge pull request #9951 from alalek:fix_bilateral_f32_simd 7 years ago
platforms OpenCV version++ 8 years ago
samples Merge pull request #9845 from dkurt:fast_neural_style_models 7 years ago
.gitattributes build: added VERSIONINFO resource 8 years ago
.gitignore .gitignore: added ".cache" directory back 8 years ago
.tgitconfig Add tgit.icon project config 11 years ago
CMakeLists.txt cmake: disable generation of pkg-config file during Xcode build 7 years ago
CONTRIBUTING.md migration: github.com/opencv/opencv 9 years ago
LICENSE Update license year range to 2016 9 years ago
README.md Improve README (#9243) 8 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.