mirror/opencv
1
0
Fork 0
mirror of https://github.com/opencv/opencv.git synced 2024-11-27 12:40:05 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
Open Source Computer Vision Library
26,246 Commits 6 Branches 126 Tags 3 GiB
C++ 87%
C 3.4%
Python 2.8%
CMake 2.1%
Java 1.6%
Other 2.9%
b761ec0132
Go to file
Alexander Alekhin b761ec0132 Merge pull request #14177 from alalek:fix_14173
2019-03-28 14:57:07 +00:00
.github Merge pull request #12093 from CYTing1998:update_issue 2018-08-03 20:08:30 +03:00
3rdparty Merge remote-tracking branch 'upstream/3.4' into merge-3.4 2019-03-26 18:56:54 +00:00
apps spelling fixes 2019-02-11 15:35:10 +03:00
cmake Merge remote-tracking branch 'upstream/3.4' into merge-3.4 2019-03-26 18:56:54 +00:00
data Some mist. typo fixes 2018-02-07 06:59:15 -05:00
doc Merge remote-tracking branch 'upstream/3.4' into merge-3.4 2019-03-22 19:31:31 +03:00
include drop legacy headers 2018-09-10 08:33:16 +00:00
modules Merge pull request #14177 from alalek:fix_14173 2019-03-28 14:57:07 +00:00
platforms android: build package with API 21 2019-03-20 19:21:43 +03:00
samples Merge remote-tracking branch 'upstream/3.4' into merge-3.4 2019-03-26 18:56:54 +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 git: .gitignore update 2017-11-07 17:24:48 +03:00
CMakeLists.txt Merge remote-tracking branch 'upstream/3.4' into merge-3.4 2019-03-26 18:56:54 +00:00
CONTRIBUTING.md migration: github.com/opencv/opencv 2016-07-12 12:51:12 +03:00
LICENSE copyright: 2019 2019-01-02 01:20:38 +00:00
README.md Use secure URLs in README (#12160) 2018-08-31 17:09:40 +03: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.