mirror/opencv
1
0
Fork 0
mirror of https://github.com/opencv/opencv.git synced 2024-11-25 11:40:44 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
Open Source Computer Vision Library
28,214 Commits 6 Branches 126 Tags 3 GiB
C++ 87%
C 3.4%
Python 2.8%
CMake 2.1%
Java 1.6%
Other 2.9%
5340dc6686
Go to file
Alexander Alekhin 5340dc6686 Merge pull request #19819 from alalek:cmake_fix_headers_order
2021-04-01 01:34:21 +00:00
.github Updated more links to forum.opencv.org 2021-01-19 21:55:45 +03:00
3rdparty ffmpeg/3.4: update FFmpeg wrapper 2021.03 2021-03-02 23:59:38 +00:00
apps Fix typo 'Applicatioin' 2020-11-17 15:02:55 +00:00
cmake Merge pull request #19819 from alalek:cmake_fix_headers_order 2021-04-01 01:34:21 +00:00
data fix files permissions 2020-04-13 04:29:55 +00:00
doc Merge pull request #18952 from terfendail:wui_doc 2021-03-30 16:18:03 +00:00
include add missing DNN header to opencv2/opencv.hpp 2018-02-15 15:59:14 +01:00
modules Merge pull request #19814 from alalek:pyopencv_to_safe 2021-03-31 22:58:18 +00:00
platforms build: winpack_dldt with dldt 2021.3.0 2021-03-26 08:58:00 +00:00
samples ml: use OpenCV license header for logistic regression 2021-03-17 20:29:52 +00:00
.editorconfig add .editorconfig 2018-10-11 17:57:51 +00:00
.gitattributes cmake: generate and install ffmpeg-download.ps1 2018-06-09 13:19:48 +03:00
.gitignore Ignore Visual Studio cmake configuration file 2020-03-17 21:12:54 +03:00
CMakeLists.txt cmake: update Python linters handling 2021-03-05 12:54:51 +00:00
CONTRIBUTING.md migration: github.com/opencv/opencv 2016-07-12 12:51:12 +03:00
LICENSE copyright: 2021 2021-01-01 13:40:32 +00:00
README.md update forum link 2021-01-11 18:39:46 +00:00

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.