Open Source Computer Vision Library
Go to file
Cartucho 7267e94be7 Merge pull request #9736 from Cartucho/const_and_class_to_json
* Adding constants to json file

* adding sub-module to constants name

* adding namespace to functions

* adding namespace to classes

* remove namespace from methods

* static methods

* python signatures generation

* python: more fixes for signatures generation

Python names existence can be checked via command:

    python -c "import cv2 as cv; print(repr(<py_name>))"
2017-11-04 06:38:18 +03:00
.github migration: github.com/opencv/opencv 2016-07-12 12:51:12 +03:00
3rdparty Updated TBB package to 2018.1 2017-10-20 12:16:06 +03:00
apps Edit spelling mistake in my previous pull request 2017-10-22 12:37:19 +05:30
cmake VisualStudio: Added solution folders for dispatched optimization targets 2017-10-30 18:30:20 +03:00
data fixing models to resolve XML violation issue 2017-06-13 09:42:15 +02:00
doc improve doc. 2017-10-31 10:30:01 +01:00
include Merge pull request #7370 from souch55:Fixxn 2016-10-01 10:44:56 +00:00
modules Merge pull request #9736 from Cartucho/const_and_class_to_json 2017-11-04 06:38:18 +03:00
platforms OpenCV version++ 2017-10-10 12:29:57 +03:00
samples Merge pull request #9941 from catree:improve_dnn_samples 2017-10-30 09:58:18 +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 Merge pull request #9864 from mapreri:multiarch 2017-10-30 15:43:42 +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

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.