generic-library/opencv
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
13,109 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%
3578f0afe9
Go to file
Alexander Alekhin 3578f0afe9 ocl: workaround for synchronization issue in ::map()
2014-04-11 13:09:18 +04:00
3rdparty Merge pull request #2403 from hbristow:issue-3451 2014-03-28 12:13:14 +04:00
apps Merge remote-tracking branch 'origin/2.4' into merge-2.4 2014-01-27 15:28:14 +04:00
cmake Merge pull request #2390 from nicolasmartin3d:master_bug3546 2014-04-10 13:33:43 +04:00
data Merge remote-tracking branch 'origin/2.4' into merge-2.4 2014-02-11 12:05:01 +04:00
doc Merge pull request #2538 from ElenaGvozdeva:ipp_async_convert 2014-04-08 11:05:30 +04:00
include Merge remote-tracking branch 'origin/2.4' into merge-2.4 2014-01-27 15:28:14 +04:00
modules ocl: workaround for synchronization issue in ::map() 2014-04-11 13:09:18 +04:00
platforms Merge remote-tracking branch 'origin/2.4' into merge-2.4 2014-04-07 14:59:34 +04:00
samples TAPI: stitching: improve warpers 2014-04-11 13:01:07 +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 ipp: added support for updated ICV package 2014-04-09 18:20:49 +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.