Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

Tree [0a90d6] /
History



File Date Author Commit
3rdparty 2014-02-14 Stuart Cunningham Stuart Cunningham [145484] Fix build of libtiff on big endian host due to ...
apps 2014-01-17 Alexander Smorkalov Alexander Smorkalov [b75cbf] All installed files marked with component names...
cmake 2014-02-13 Stuart Cunningham Stuart Cunningham [55b9c0] Fix cmake detection of build platform endianness
data 2014-02-06 Alexander Smorkalov Alexander Smorkalov [b86088] Implicit testdata directory permissions setup a...
doc 2014-02-12 Martin Dlouhy Martin Dlouhy [d9a322] undo changes of cv2.cv.* functions/constants
include 2014-01-17 Alexander Smorkalov Alexander Smorkalov [b75cbf] All installed files marked with component names...
modules 2014-02-21 Vadim Pisarevsky Vadim Pisarevsky [51dafc] fixed hint type declaration
platforms 2014-01-30 Alexander Smorkalov Alexander Smorkalov [c81504] Android toolchain file sync with original project.
samples 2014-02-14 Roman Donchenko Roman Donchenko [88f993] Deleted an assignment to a variable that doesn'...
.gitattributes 2013-09-14 hbristow hbristow [224f44] Made changes to OpenCVFindMatlab suggested by S...
.gitignore 2014-01-10 Ilya Lavrenov Ilya Lavrenov [f197d8] updated .gitignore
CMakeLists.txt 2014-02-13 Stuart Cunningham Stuart Cunningham [55b9c0] Fix cmake detection of build platform endianness
LICENSE 2014-01-18 Alexander Smorkalov Alexander Smorkalov [7821fe] Initial Linux packages build rools for CPack.
README.md 2014-02-15 Kirill Kornyakov Kirill Kornyakov [ed1aa7] Replaced Gittip button
index.rst 2013-09-21 abidrahmank abidrahmank [899781] GSoC Python Tutorials

Read Me

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.