mirror/opencv
1
0
Fork 0
mirror of https://github.com/opencv/opencv.git synced 2024-11-25 03:30:34 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
Open Source Computer Vision Library
24,221 Commits 6 Branches 126 Tags 3 GiB
C++ 87%
C 3.4%
Python 2.8%
CMake 2.1%
Java 1.6%
Other 2.9%
86885c5ed0
Go to file
Alexander Alekhin 86885c5ed0 Merge pull request #11859 from alalek:fix_videoio_msmf_win7
2018-06-30 04:50:31 +00:00
.github migration: github.com/opencv/opencv 2016-07-12 12:51:12 +03:00
3rdparty Merge pull request #11808 from tomoaki0705:caroteneSuppressWarnings 2018-06-23 08:46:29 +00:00
apps cmake: function for application creation (#11736) 2018-06-25 17:02:58 +03:00
cmake python: support standalone Python bindings build 2018-06-07 15:16:39 +03:00
data Some mist. typo fixes 2018-02-07 06:59:15 -05:00
doc Add Java and Python code for Image Segmentation with Distance Transform and Watershed Algorithm tutorial. Use more Pythonic code. 2018-06-27 18:48:32 +02:00
include add missing DNN header to opencv2/opencv.hpp 2018-02-15 15:59:14 +01:00
modules videoio(MSMF): avoid OpenCV load failure on Win7 machines 2018-06-29 20:22:26 +00:00
platforms Fixed a typo in android toolchain documentation. 2018-06-01 12:39:34 +03:00
samples Set output layers names and types for models in DLDT's intermediate representation 2018-06-28 10:21:45 +03:00
.gitattributes cmake: generate and install ffmpeg-download.ps1 2018-06-09 13:19:48 +03:00
.gitignore git: .gitignore update 2017-11-07 17:24:48 +03:00
CMakeLists.txt Merge pull request #11636 from alalek:cmake_ffmpeg_find_package 2018-06-04 14:37:36 +00:00
CONTRIBUTING.md migration: github.com/opencv/opencv 2016-07-12 12:51:12 +03:00
LICENSE copyright: 2018 2018-01-16 13:55:42 +03:00
README.md Improve README (#9243) 2017-09-13 17:58:34 +03:00

README.md

OpenCV: Open Source Computer Vision Library

Resources

Contributing

Please read the contribution guidelines before starting work on a pull request.

Summary of the 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.