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.
21529 Commits
7 Branches
126 Tags
3.0 GiB
 
 
 
 
 
 
Tag: Branch: Tree: fab4f4b9d5
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'fab4f4b9d5'
${ noResults }
Go to file
Aleksandr Rybnikov fab4f4b9d5
Disabled logging in caffe parser in release 		7 years ago
.github migration: github.com/opencv/opencv 8 years ago
3rdparty Fixing some static analysis issues 7 years ago
apps trace: initial support for code trace 7 years ago
cmake Merge pull request #8990 from mshabunin:fix-static-2 7 years ago
data fixing models to resolve XML violation issue 8 years ago
doc core: add an ability to use cxx11 lambda as a parallel_for_ body 7 years ago
include Merge pull request #7370 from souch55:Fixxn 8 years ago
modules Disabled logging in caffe parser in release 7 years ago
platforms Merge pull request #8386 from jtkb:feature/cmake-maven-it-module 8 years ago
samples Merge pull request #9017 from sovrasov:parallel_for_cxx11 7 years ago
.gitattributes build: added VERSIONINFO resource 8 years ago
.gitignore .gitignore: added ".cache" directory back 8 years ago
.tgitconfig
…
CMakeLists.txt trace: initial support for code trace 7 years ago
CONTRIBUTING.md migration: github.com/opencv/opencv 8 years ago
LICENSE Update license year range to 2016 9 years ago
README.md migration: github.com/opencv/opencv 8 years ago

README.md

OpenCV: Open Source Computer Vision Library

Resources

Contributing

Please read before starting work on a pull request: https://github.com/opencv/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.