mirror/opencv
1
0
Fork 0
mirror of https://github.com/opencv/opencv.git synced 2024-11-30 14:29:49 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
Open Source Computer Vision Library
25,163 Commits 6 Branches 126 Tags 3 GiB
C++ 87%
C 3.4%
Python 2.8%
CMake 2.1%
Java 1.6%
Other 2.9%
2180a67670
Go to file
Alexander Alekhin 2180a67670 Merge pull request #12863 from alalek:disable_wshadow_gcc_4.x
2018-10-17 13:59:13 +00:00
.github Merge pull request #12093 from CYTing1998:update_issue 2018-08-03 20:08:30 +03:00
3rdparty core: follow IEEE 754 rules for floating-point division 2018-10-14 10:47:50 +00:00
apps Fixed several incorrect printf format specifiers 2018-09-24 11:31:40 +03:00
cmake build: eliminate warnings 2018-10-17 08:43:18 +00:00
data Some mist. typo fixes 2018-02-07 06:59:15 -05:00
doc Merge remote-tracking branch 'upstream/3.4' into merge-3.4 2018-10-02 14:31:05 +03:00
include drop legacy headers 2018-09-10 08:33:16 +00:00
modules Merge pull request #12838 from dmatveev:gapi_fluid_resize_lpi 2018-10-17 09:22:28 +00:00
platforms Merge remote-tracking branch 'upstream/3.4' into merge-3.4 2018-10-15 20:15:42 +00:00
samples Merge remote-tracking branch 'upstream/3.4' into merge-3.4 2018-10-15 20:15:42 +00: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 remote-tracking branch 'upstream/3.4' into merge-3.4 2018-10-12 10:05:55 +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 Use secure URLs in README (#12160) 2018-08-31 17:09:40 +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.