mirror/opencv
1
0
Fork 0
mirror of https://github.com/opencv/opencv.git synced 2024-12-02 07:39:57 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
Open Source Computer Vision Library
22,199 Commits 6 Branches 126 Tags 3 GiB
C++ 87%
C 3.4%
Python 2.8%
CMake 2.1%
Java 1.6%
Other 2.9%
8f05af8d05
Go to file
Jacob MacRitchie 8f05af8d05 Fixed my additions. For real this time. I think. 
Oops. Hopefully it works this time.
2017-09-24 05:58:22 -03:00
.github migration: github.com/opencv/opencv 2016-07-12 12:51:12 +03:00
3rdparty Do not enable asm with clang 2017-09-19 18:09:30 -07:00
apps cmake: drop INSTALL_NAME_DIR 2017-08-22 15:26:20 +03:00
cmake Update OpenCVDownload.cmake unpack 2017-09-21 14:00:43 +02:00
data fixing models to resolve XML violation issue 2017-06-13 09:42:15 +02:00
doc Fixed my additions. For real this time. I think. 2017-09-24 05:58:22 -03:00
include Merge pull request #7370 from souch55:Fixxn 2016-10-01 10:44:56 +00:00
modules Merge pull request #9618 from vipinanand4:goodFeaturesToTrack_added_gradiantSize 2017-09-22 14:04:43 +00:00
platforms Removed hard-coded version from integration test. (#9335) 2017-09-13 17:19:16 +03:00
samples Merge pull request #9618 from vipinanand4:goodFeaturesToTrack_added_gradiantSize 2017-09-22 14:04:43 +00: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 python(test): enable pylint checks for tests 2017-09-03 18:19:17 +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 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.