mirror/opencv
1
0
Fork 0
mirror of https://github.com/opencv/opencv.git synced 2024-12-15 01:39:10 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
Open Source Computer Vision Library
21,821 Commits 6 Branches 127 Tags 3 GiB
C++ 87%
C 3.4%
Python 2.8%
CMake 2.1%
Java 1.6%
Other 2.9%
5375a77f84
Go to file
Vladislav Sovrasov 5375a77f84 core: add multi-argument CV_Assert
2017-08-03 15:31:05 +03:00
.github migration: github.com/opencv/opencv 2016-07-12 12:51:12 +03:00
3rdparty Merge pull request #9237 from alalek:fix_winrt_build 2017-07-26 10:42:49 +00:00
apps trace: initial support for code trace 2017-06-26 17:07:13 +03:00
cmake cmake: fix compiler flags 2017-07-26 17:21:46 +03:00
data fixing models to resolve XML violation issue 2017-06-13 09:42:15 +02:00
doc Merge pull request #9246 from bragboy:patch-1 2017-08-02 20:22:11 +00:00
include Merge pull request #7370 from souch55:Fixxn 2016-10-01 10:44:56 +00:00
modules core: add multi-argument CV_Assert 2017-08-03 15:31:05 +03:00
platforms fix OpenCV GitHub repository URL 2017-07-31 17:48:57 +03:00
samples Honor fixing principal point in camera calib tutorial. 2017-08-01 10:35:18 -05:00
.gitattributes build: added VERSIONINFO resource 2017-06-20 15:45:21 +03:00
.gitignore .gitignore: added ".cache" directory back 2017-06-21 19:03:17 +03:00
.tgitconfig Add tgit.icon project config 2014-02-26 17:46:52 +08:00
CMakeLists.txt minimal CMake version => 2.8.12.2 2017-07-21 14:06:19 +03: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.