mirror/opencv
1
0
Fork 0
mirror of https://github.com/opencv/opencv.git synced 2024-12-24 00:17:59 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
Open Source Computer Vision Library
25,731 Commits 6 Branches 127 Tags 3 GiB
C++ 87%
C 3.4%
Python 2.8%
CMake 2.1%
Java 1.6%
Other 2.9%
dfb9832a25
Go to file
Alexander Alekhin dfb9832a25 cmake(protobuf): ensure using of own headers
2019-04-15 22:28:33 +00:00
.github migration: github.com/opencv/opencv 2016-07-12 12:51:12 +03:00
3rdparty cmake(protobuf): ensure using of own headers 2019-04-15 22:28:33 +00:00
apps Merge pull request #13709 from michal-kowalczyk:flush-processed-samples-number 2019-04-12 18:51:35 +03:00
cmake Merge pull request #14078 from alalek:test_python_from_modules 2019-04-12 11:39:12 +00:00
data Some mist. typo fixes 2018-02-07 06:59:15 -05:00
doc Merge pull request #14297 from shxuy:patch-1 2019-04-12 19:32:08 +03:00
include add missing DNN header to opencv2/opencv.hpp 2018-02-15 15:59:14 +01:00
modules Merge pull request #14255 from l-bat:networks_visualization 2019-04-12 19:31:07 +03:00
platforms ts: test tags for flexible/reliable tests filtering 2019-04-08 19:12:49 +00:00
samples docs: fix links 2019-04-04 18:57:22 +03: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 cmake: fix licenses install rules 2019-04-02 19:24:14 +03:00
CONTRIBUTING.md migration: github.com/opencv/opencv 2016-07-12 12:51:12 +03:00
LICENSE copyright: 2019 2019-01-02 01:18:04 +00:00
README.md Improve README (#9243) 2017-09-13 17:58:34 +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.