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.
28927 Commits
6 Branches
126 Tags
3.0 GiB
 
 
 
 
 
 
Tag: Branch: Tree: 766f58ed7e
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '766f58ed7e'
${ noResults }
Go to file
OpenCV Pushbot 766f58ed7e
Merge pull request #21980 from asenyaev:asen/move_variables_to_the_host 		3 years ago
.github Move environment variables on a host side (GHA Windows) 3 years ago
3rdparty Fix some typos in doc. 3 years ago
apps Fix typo 'Applicatioin' 4 years ago
cmake build(winpack_dldt): force using CMake config for InferenceEngine 3 years ago
data fix files permissions 5 years ago
doc Merge pull request #21964 from Julian-Sz:patch-1 3 years ago
include add missing DNN header to opencv2/opencv.hpp 7 years ago
modules Merge pull request #21935 from Yulv-git:3.4-typos3 3 years ago
platforms build(winpack_dldt): force using CMake config for InferenceEngine 3 years ago
samples Update text_detection.py 3 years ago
.editorconfig add .editorconfig 6 years ago
.gitattributes cmake: generate and install ffmpeg-download.ps1 7 years ago
.gitignore Ignore Visual Studio cmake configuration file 5 years ago
CMakeLists.txt Merge pull request #21562 from alalek:cmake_carotene_use_cv_disable_optimization 3 years ago
CONTRIBUTING.md migration: github.com/opencv/opencv 9 years ago
LICENSE copyright: 2022 3 years ago
README.md update forum link 4 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.