Open Source Computer Vision Library
Go to file
Vadim Levin ccebbbc0ac feature: submodule or a class scope for exported classes
All classes are registered in the scope that corresponds to C++
namespace or exported class.

Example:
`cv::ml::Boost` is exported as `cv.ml.Boost`
`cv::SimpleBlobDetector::Params` is exported as
`cv.SimpleBlobDetector.Params`

For backward compatibility all classes are registered in the global
module with their mangling name containing scope information.
Example:
`cv::ml::Boost` has `cv.ml_Boost` alias to `cv.ml.Boost` type
2022-03-02 14:30:52 +03:00
.github Updated more links to forum.opencv.org 2021-01-19 21:55:45 +03:00
3rdparty ffmpeg/3.4: update FFmpeg wrapper 2021.12 2021-12-20 15:32:05 +00:00
apps Fix typo 'Applicatioin' 2020-11-17 15:02:55 +00:00
cmake build(winpack_dldt): force using CMake config for InferenceEngine 2022-02-11 13:07:25 +00:00
data fix files permissions 2020-04-13 04:29:55 +00:00
doc Merge pull request #21320 from catree:solvePnP_doc_page 2021-12-24 11:55:34 +00:00
include add missing DNN header to opencv2/opencv.hpp 2018-02-15 15:59:14 +01:00
modules feature: submodule or a class scope for exported classes 2022-03-02 14:30:52 +03:00
platforms build(winpack_dldt): force using CMake config for InferenceEngine 2022-02-11 13:07:25 +00:00
samples Update text_detection.py 2022-02-09 17:14:05 +01:00
.editorconfig add .editorconfig 2018-10-11 17:57:51 +00:00
.gitattributes cmake: generate and install ffmpeg-download.ps1 2018-06-09 13:19:48 +03:00
.gitignore Ignore Visual Studio cmake configuration file 2020-03-17 21:12:54 +03:00
CMakeLists.txt Merge pull request #21562 from alalek:cmake_carotene_use_cv_disable_optimization 2022-02-03 19:18:26 +00:00
CONTRIBUTING.md migration: github.com/opencv/opencv 2016-07-12 12:51:12 +03:00
LICENSE copyright: 2022 2022-01-04 12:48:27 +00:00
README.md update forum link 2021-01-11 18:39:46 +00: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.