mirror/opencv
1
0
Fork 0
mirror of https://github.com/opencv/opencv.git synced 2024-11-29 22:00:25 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
Open Source Computer Vision Library
15,085 Commits 6 Branches 126 Tags 3 GiB
C++ 87%
C 3.4%
Python 2.8%
CMake 2.1%
Java 1.6%
Other 2.9%
986878a881
Go to file
Vadim Pisarevsky 986878a881 Merge pull request #3422 from avdmitry:install_doc_update
2014-11-16 18:08:35 +00:00
3rdparty update IPPICV package 2014-11-05 13:26:23 +03:00
apps Several type of formal refactoring: 2014-08-13 15:21:35 +04:00
cmake Fix Cuda -Wl linker options 2014-11-11 12:12:28 -05:00
data moved part of video to contrib/{outflow, bgsegm}; moved matlab to contrib 2014-08-10 23:24:16 +04:00
doc updated linux installation documentation 2014-11-14 12:32:42 +03:00
include Split highgui module to videoio and highgui 2014-07-14 23:16:47 +04:00
modules Merge pull request #3399 from mshabunin:doxygen-core 2014-11-13 07:25:27 +00:00
platforms Fixing iOS clang warnings, part 3 2014-10-17 18:15:21 +04:00
samples fix gpu performance sample compilation 2014-11-12 18:07:20 +03:00
.gitattributes Made changes to OpenCVFindMatlab suggested by SpecLad 2013-09-14 13:32:15 +10:00
.gitignore Merge remote-tracking branch 'origin/2.4' into merge-2.4 2014-01-14 11:53:59 +04:00
.tgitconfig Add tgit.icon project config 2014-02-26 17:46:52 +08:00
CMakeLists.txt Basic doxygen documentation support 2014-10-22 15:24:15 +04:00
index.rst GSoC Python Tutorials 2013-09-23 13:41:14 +05:30
LICENSE adding LICENSE file and a sample of its reference in ocl.hpp 2013-12-18 19:33:25 +04:00
README.md Replaced Gittip button 2014-02-15 13:10:09 +04:00

README.md

OpenCV: Open Source Computer Vision Library

Gittip

Resources

Contributing

Please read before starting work on a pull request: http://code.opencv.org/projects/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.