mirror/opencv
1
0
Fork 0
mirror of https://github.com/opencv/opencv.git synced 2024-11-30 06:10:02 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
Open Source Computer Vision Library
15,708 Commits 6 Branches 126 Tags 3 GiB
C++ 87%
C 3.4%
Python 2.8%
CMake 2.1%
Java 1.6%
Other 2.9%
16f36a5fda
Go to file
Olexa Bilaniuk 16f36a5fda Replaced division by reciprocal + multiply in a few places.
2015-03-03 11:55:36 -05:00
3rdparty aarch64 support 2015-02-26 19:43:32 +03:00
apps Merge pull request #3709 from StevenPuttemans:fix_traincascade_load_message_master 2015-02-24 12:50:38 +00:00
cmake Python support 2015-03-02 18:13:00 +03:00
data fixing CUDA cascade classifiers function and needed models 2015-02-27 14:20:27 +01:00
doc Merge pull request #3690 from theodr:moprh_lines_detection_tut 2015-03-02 11:36:15 +00:00
include Split highgui module to videoio and highgui 2014-07-14 23:16:47 +04:00
modules Replaced division by reciprocal + multiply in a few places. 2015-03-03 11:55:36 -05:00
platforms Support for compound modules, support for contrib_world 2015-02-10 18:30:05 +03:00
samples Merge pull request #3690 from theodr:moprh_lines_detection_tut 2015-03-02 11:36:15 +00:00
.gitattributes Made changes to OpenCVFindMatlab suggested by SpecLad 2013-09-14 13:32:15 +10:00
.gitignore Merge remote-tracking branch 'origin/2.4' into merge-2.4 2014-01-14 11:53:59 +04:00
.tgitconfig Add tgit.icon project config 2014-02-26 17:46:52 +08:00
CMakeLists.txt aarch64 support 2015-02-26 19:43:32 +03:00
LICENSE adding LICENSE file and a sample of its reference in ocl.hpp 2013-12-18 19:33:25 +04:00
README.md Replaced Gittip button 2014-02-15 13:10:09 +04:00

README.md

OpenCV: Open Source Computer Vision Library

Gittip

Resources

Contributing

Please read before starting work on a pull request: http://code.opencv.org/projects/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.