third_party/opencv
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
22,055 Commits 3 Branches 0 Tags 516 MiB
C++ 92.6%
C 6.8%
CMake 0.5%
Objective-C 0.1%
44b75eb116
Go to file
Alexander Alekhin 44b75eb116 core: fix OpenCL runtime compilation with HAVE_OPENCL_STATIC
2017-09-08 12:43:33 +03:00
.github migration: github.com/opencv/opencv 2016-07-12 12:51:12 +03:00
3rdparty Merge pull request #9395 from lupustr3:pvlasov/icv2017u3_update 2017-08-24 11:48:53 +00:00
apps cmake: drop INSTALL_NAME_DIR 2017-08-22 15:26:20 +03:00
cmake Merge pull request #9457 from alalek:type_traits_issue_7599 2017-09-06 13:34:29 +00:00
data fixing models to resolve XML violation issue 2017-06-13 09:42:15 +02:00
doc Merge pull request #9457 from alalek:type_traits_issue_7599 2017-09-06 13:34:29 +00:00
include Merge pull request #7370 from souch55:Fixxn 2016-10-01 10:44:56 +00:00
modules core: fix OpenCL runtime compilation with HAVE_OPENCL_STATIC 2017-09-08 12:43:33 +03:00
platforms cmake: change Pylint integration 2017-08-24 14:59:33 +03:00
samples Merge pull request #9476 from dkurt:tutorial_dnn_android 2017-09-03 10:34:25 +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 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.