mirror/opencv
1
0
Fork 0
mirror of https://github.com/opencv/opencv.git synced 2024-11-29 13:47:32 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
Open Source Computer Vision Library
18,690 Commits 6 Branches 126 Tags 3 GiB
C++ 87%
C 3.4%
Python 2.8%
CMake 2.1%
Java 1.6%
Other 2.9%
f819323296
Go to file
Balint Cristian f819323296 Fix AGAST keypoint declared size.
2016-03-12 16:49:14 +02:00
.github move GitHub templates into .github folder 2016-03-04 14:20:25 +03:00
3rdparty make Xcode 7.2 happy. 2016-01-13 20:19:19 +08:00
apps missing break statement 2016-03-04 09:41:13 +01:00
cmake Merge pull request #6060 from alalek:fix_opencl_opengl_sharing_6052 2016-02-16 07:10:02 +00:00
data Fix the missing - in file. 2016-02-18 11:28:41 +01:00
doc Merge pull request #6190 from berak:fix_ml_python_tutorial 2016-03-01 14:05:42 +00:00
include include available modules only 2016-01-20 13:07:46 +03:00
modules Fix AGAST keypoint declared size. 2016-03-12 16:49:14 +02:00
platforms Merge pull request #5923 from powderluv:master 2016-01-14 12:07:02 +00:00
samples Merge pull request #6118 from Emoters:hotfix/planar_tutorial_fixes 2016-03-03 17:24:08 +00: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: remove non-ascii symbols 2016-02-09 14:44:05 +03:00
CONTRIBUTING.md add link to contributing guidelines 2015-09-17 14:15:20 +02:00
LICENSE Update license year range to 2016 2016-01-18 10:11:01 +05:30
README.md Removed gittip link 2016-02-08 11:04:19 +03:00

README.md

OpenCV: Open Source Computer Vision Library

Resources

Contributing

Please read before starting work on a pull request: https://github.com/Itseez/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.