mirror/opencv
1
0
Fork 0
mirror of https://github.com/opencv/opencv.git synced 2025-06-27 15:01:50 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
Open Source Computer Vision Library
19,552 Commits 6 Branches 128 Tags 3.2 GiB
C++ 87.7%
C 3.2%
Python 2.6%
CMake 2%
Java 1.5%
Other 2.8%
83b36bfd79
Go to file
ggargov 83b36bfd79 Added comments to clarify sample code 
Program flow is not easily apparent so hopefully ANY comments in the code could help new users.
2016-08-09 18:08:58 +03:00
.github migration: github.com/opencv/opencv 2016-07-12 12:51:12 +03:00
3rdparty Merge pull request #6899 from alalek:ffmpeg_update 2016-07-21 07:31:11 +00:00
apps allow for screen size related resizing 2016-08-02 10:44:01 +02:00
cmake cmake: add OPENCV_ENABLE_NONFREE option and macro 2016-08-04 19:23:49 +03:00
data Fix the missing - in file. 2016-02-18 11:28:41 +01:00
doc Merge pull request #7059 from berak:doc_python_drawkeypoints 2016-08-08 15:31:11 +00:00
include fixing issues 2016-08-08 12:12:35 +02:00
modules Merge pull request #7044 from wolever:master 2016-08-09 12:59:38 +00:00
platforms Merge pull request #6827 from jtkb:cmake-maven-release 2016-07-18 08:56:26 +00:00
samples Added comments to clarify sample code 2016-08-09 18:08:58 +03:00
.gitattributes Made changes to OpenCVFindMatlab suggested by SpecLad 2013-09-14 13:32:15 +10:00
.gitignore Improved thrust interop tutorial. 2015-09-24 09:32:38 -04:00
.tgitconfig Add tgit.icon project config 2014-02-26 17:46:52 +08:00
CMakeLists.txt cmake: add OPENCV_ENABLE_NONFREE option and macro 2016-08-04 19:23:49 +03:00
CONTRIBUTING.md migration: github.com/opencv/opencv 2016-07-12 12:51:12 +03:00
LICENSE Update license year range to 2016 2016-01-18 10:11:01 +05:30
README.md migration: github.com/opencv/opencv 2016-07-12 12:51:12 +03:00

README.md

OpenCV: Open Source Computer Vision Library

Resources

Contributing

Please read before starting work on a pull request: https://github.com/opencv/opencv/wiki/How_to_contribute

Summary of 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.