mirror/opencv
1
0
Fork 0
mirror of https://github.com/opencv/opencv.git synced 2024-11-28 21:20:18 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
Open Source Computer Vision Library
19,932 Commits 6 Branches 126 Tags 3 GiB
C++ 87%
C 3.4%
Python 2.8%
CMake 2.1%
Java 1.6%
Other 2.9%
48ae99ecef
Go to file
ArkadiuszRaj 48ae99ecef Support for MONO8 & MONO12 pixel formats
2016-10-08 13:01:01 +02:00
.github migration: github.com/opencv/opencv 2016-07-12 12:51:12 +03:00
3rdparty Added support for OpenVX 1.0, updated cmake part, minor fixes 2016-10-04 15:31:54 +03:00
apps Merge pull request #7370 from souch55:Fixxn 2016-10-01 10:44:56 +00:00
cmake Basic support for GigE cameras via Aravis SDK 2016-10-07 21:55:49 +02:00
data Removing whitespace to appease doc builder 2016-08-12 00:31:50 -03:00
doc Merge pull request #7368 from berak:py_tutorials_fix 2016-10-01 15:40:54 +00:00
include Merge pull request #7370 from souch55:Fixxn 2016-10-01 10:44:56 +00:00
modules Support for MONO8 & MONO12 pixel formats 2016-10-08 13:01:01 +02:00
platforms Merge pull request #7358 from convoyinc:ios-framework-module-exclusion 2016-10-02 11:38:59 +00:00
samples supress numpy future warning with None comparison 2016-09-14 21:39:11 +03: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 Basic support for GigE cameras via Aravis SDK 2016-10-07 21:55:49 +02:00
CONTRIBUTING.md migration: github.com/opencv/opencv 2016-07-12 12:51:12 +03:00
LICENSE Update license year range to 2016 2016-01-18 10:11:01 +05:30
README.md migration: github.com/opencv/opencv 2016-07-12 12:51:12 +03:00

README.md

OpenCV: Open Source Computer Vision Library

Resources

Contributing

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