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.
27777 Commits
7 Branches
126 Tags
3.0 GiB
 
 
 
 
 
 
Tag: Branch: Tree: a6e15b2f57
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'a6e15b2f57'
${ noResults }
Go to file
Alexander Alekhin a6e15b2f57
cmake: prefer using Eigen configuration files 		4 years ago
.github migration: github.com/opencv/opencv 8 years ago
3rdparty cmake(3rdparty): use EXCLUDE_FROM_ALL 4 years ago
apps cmake(apps): support OPENCV_INSTALL_APPS_LIST 5 years ago
cmake cmake: prefer using Eigen configuration files 4 years ago
data fix files permissions 5 years ago
doc Bugfix: Manual page sizes now overwrite the default page size if they are both specified. Remove redudant .upper() call, 1 to 1 key matching enforced 4 years ago
include add missing DNN header to opencv2/opencv.hpp 7 years ago
modules fix curved qrcodes decoding 4 years ago
platforms Merge pull request #18068 from lionkunonly:gsoc_2020_simd 4 years ago
samples fixes #18613 4 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 Install: added prebuilt samples installation 4 years ago
CONTRIBUTING.md migration: github.com/opencv/opencv 8 years ago
LICENSE copyright: 2020 5 years ago
README.md 3.4 docs for 3.4 branch 5 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.