generic-library/opencv
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
14,285 Commits 3 Branches 47 Tags 422 MiB
C++ 83.4%
Cuda 5.9%
C 3.8%
Java 2.4%
CMake 2.2%
Other 2.1%
dea40e5e99
Go to file
Vadim Pisarevsky dea40e5e99 Merge pull request #3086 from fpuja:pragma_warning4127_fixing
2014-08-16 16:50:41 +00:00
3rdparty Merge pull request #2925 from BloodAxe:osx-framework-script 2014-07-19 18:04:15 +00:00
apps Several type of formal refactoring: 2014-08-13 15:21:35 +04:00
cmake Merge pull request #3098 from jet47:fix-cuda-compilation 2014-08-14 10:05:49 +00:00
data moved part of video to contrib/{outflow, bgsegm}; moved matlab to contrib 2014-08-10 23:24:16 +04:00
doc Python bindings tutorial 2014-08-16 16:40:18 +05:30
include Split highgui module to videoio and highgui 2014-07-14 23:16:47 +04:00
modules Merge pull request #3086 from fpuja:pragma_warning4127_fixing 2014-08-16 16:50:41 +00:00
platforms Fix cmake to build OpenCV framework on OSX 2014-07-01 22:31:57 +03:00
samples trying to solve compile problems; temporarily disabled some tests for just added optimization algo's 2014-08-14 14:37:30 +04: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 Merge with master and fix conflicts 2014-08-13 18:24:11 +04:00
index.rst GSoC Python Tutorials 2013-09-23 13:41:14 +05:30
LICENSE Initial Linux packages build rools for CPack. 2014-01-21 20:34:36 +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.