mirror/opencv
1
0
Fork 0
mirror of https://github.com/opencv/opencv.git synced 2025-06-07 09:25:45 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
Open Source Computer Vision Library
16,914 Commits 6 Branches 128 Tags 3.4 GiB
C++ 87.7%
C 3.2%
Python 2.6%
CMake 2%
Java 1.5%
Other 2.8%
7749eb5d1f
Go to file
Roman Donchenko 7749eb5d1f Add missing packages to the Debian conflict list 
And refactor the code to make sure that the dev and runtime package lists are
in sync.
2015-09-21 13:44:37 +02:00
3rdparty proposed change by psyill 2015-09-12 12:19:44 +02:00
apps add checks for valid input data given to parameters 2015-08-06 10:24:33 +02:00
cmake Add missing packages to the Debian conflict list 2015-09-21 13:44:37 +02:00
data move data/detect_blob.png in samples/data 2015-06-22 17:51:01 +02:00
doc Correction of minor typo. 2015-09-14 00:12:06 +08:00
include Added cmake option for abi descriptor generating (GENERATE_ABI_DESCRIPTOR) 2015-03-17 16:04:04 +03:00
modules PR #4003 2015-09-21 13:44:35 +02:00
platforms fixup! Some changes to support mingw-w64 2015-09-01 12:14:40 +03:00
samples Merge pull request #5272 from avershov:opencl-vaapi-fallback 2015-09-14 11:54:20 +00:00
.gitattributes Made changes to OpenCVFindMatlab suggested by SpecLad 2013-09-14 13:32:15 +10:00
.gitignore Added support for 'imgcodecs' module: 2015-03-31 16:31:37 +03:00
.tgitconfig Add tgit.icon project config 2014-02-26 17:46:52 +08:00
CMakeLists.txt Merge pull request #5272 from avershov:opencl-vaapi-fallback 2015-09-14 11:54:20 +00:00
LICENSE 1. Input/OutputArray optimizations; 2015-04-07 16:44:26 +03:00
README.md Update README.md 2015-08-06 14:00:24 +02:00

README.md

OpenCV: Open Source Computer Vision Library

Gittip

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.