mirror/opencv
1
0
Fork 0
mirror of https://github.com/opencv/opencv.git synced 2024-11-25 19:50:38 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
Open Source Computer Vision Library
21,372 Commits 6 Branches 126 Tags 3 GiB
C++ 87%
C 3.4%
Python 2.8%
CMake 2.1%
Java 1.6%
Other 2.9%
078b4cc971
Go to file
lewisjb 078b4cc971 Added Python Docstrings
2017-06-14 16:46:08 +10:00
.github migration: github.com/opencv/opencv 2016-07-12 12:51:12 +03:00
3rdparty TBB: fix build on ARM 2017-06-05 16:36:14 +03:00
apps Make aruco dependency optional for interactive calibration app 2017-03-22 16:20:19 +03:00
cmake cmake: add ENABLE_BUILD_HARDENING option 2017-06-08 00:39:29 +00:00
data add new frontal face detection model, VISAPP2017 contribution 2016-12-21 10:49:03 +01:00
doc Update doc build instructions for doxygen 2017-06-11 00:00:45 +10:00
include Merge pull request #7370 from souch55:Fixxn 2016-10-01 10:44:56 +00:00
modules Added Python Docstrings 2017-06-14 16:46:08 +10:00
platforms Merge pull request #8386 from jtkb:feature/cmake-maven-it-module 2017-05-24 10:17:03 +00:00
samples cmake: add ENABLE_BUILD_HARDENING option 2017-06-08 00:39:29 +00:00
.gitattributes Made changes to OpenCVFindMatlab suggested by SpecLad 2013-09-14 13:32:15 +10:00
.gitignore Removed CMake configuration files from gitignore, since builds should be performed out of source tree. 2017-05-26 18:27:21 +03:00
.tgitconfig Add tgit.icon project config 2014-02-26 17:46:52 +08:00
CMakeLists.txt cmake: add ENABLE_BUILD_HARDENING option 2017-06-08 00:39:29 +00: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.