opencv

Go to file

abidrahmank 37f4e400e4 Added cv2.boxPoints() functionality to Python bindings (Feature #2023 ) http://www.code.opencv.org/issues/2023 eg: In [3]: box = ((10,10),(5,5),0) In [4]: cv2.boxPoints(box) Out[4]: array([[ 7.5, 12.5], [ 7.5, 7.5], [ 12.5, 7.5], [ 12.5, 12.5]], dtype=float32)		2013-06-24 12:13:59 +05:30
3rdparty	Merge remote-tracking branch 'origin/2.4'	2013-05-21 17:19:23 +04:00
android	Fix build problems on MIPS and Linaro NDK.	2013-06-13 16:51:45 +04:00
apps	Merge remote-tracking branch 'origin/2.4'	2013-06-05 15:42:07 +04:00
cmake	Merge remote-tracking branch 'origin/2.4'	2013-06-19 15:25:37 +04:00
data	Merge release 2.4.4	2013-03-04 19:43:49 +04:00
doc	Merge remote-tracking branch 'origin/2.4'	2013-06-19 15:25:37 +04:00
include	Minimize usages of legacy C API inside the library	2013-04-16 12:00:02 +04:00
ios	enabled png and jpeg for iOS	2013-03-25 11:19:29 +04:00
modules	Added cv2.boxPoints() functionality to Python bindings (Feature #2023 )	2013-06-24 12:13:59 +05:30
platforms	Merge remote-tracking branch 'origin/2.4'	2013-06-19 15:25:37 +04:00
samples	Merge pull request #1014 from jet47:gpustereo-refactoring	2013-06-21 17:38:36 +04:00
.gitattributes	Fix typo in .gitattributes.	2013-06-05 13:51:11 +04:00
.gitignore	Changed the file .gitignore	2012-08-28 17:46:45 +04:00
CMakeLists.txt	Merge remote-tracking branch 'origin/2.4'	2013-06-19 15:25:37 +04:00
index.rst	android -> plarforms/android	2013-05-27 11:10:38 +04:00
README	Replace the pull request guidelines with a link to the wiki.	2013-05-27 17:48:34 +04:00

README

OpenCV: open source computer vision library

Homepage:    http://opencv.org
Online docs: http://docs.opencv.org
Q&A forum:   http://answers.opencv.org
Dev zone:    http://code.opencv.org

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.