mirror/opencv
1
0
Fork 0
mirror of https://github.com/opencv/opencv.git synced 2024-11-28 13:10:12 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
Open Source Computer Vision Library
9,411 Commits 6 Branches 126 Tags 3 GiB
C++ 87%
C 3.4%
Python 2.8%
CMake 2.1%
Java 1.6%
Other 2.9%
8e79de35a8
Go to file
Ilya Lavrenov 8e79de35a8 changes for GFTT
2014-03-13 14:57:13 +04:00
3rdparty Fix build of libtiff on big endian host due to defined but empty WORDS_BIGENDIAN macro 2014-02-14 16:16:17 +11:00
apps All installed files marked with component names for install customization. 2014-01-21 20:34:36 +04:00
cmake Merge pull request #2434 from Nerei:viz_continue 2014-03-12 16:53:42 +04:00
data Implicit testdata directory permissions setup added. 2014-02-07 14:42:35 +04:00
doc Merge pull request #2433 from ilya-lavrenov:typos 2014-03-03 12:20:35 +04:00
include All installed files marked with component names for install customization. 2014-01-21 20:34:36 +04:00
modules changes for GFTT 2014-03-13 14:57:13 +04:00
platforms typos 2014-03-04 12:47:40 +04:00
samples typos 2014-03-04 12:47:40 +04:00
.gitattributes Added more text/binary/whitespace attributes for files we have. 2013-08-21 18:59:24 +04:00
.gitignore updated .gitignore 2014-01-10 18:59:06 +04:00
.tgitconfig Add tgit.icon project config 2014-02-26 17:46:52 +08:00
CMakeLists.txt Hardcode iOS's endianness, since the TestBigEndian module doesn't work there 2014-02-24 12:13:35 +04:00
index.rst android -> plarforms/android 2013-05-27 11:10:38 +04:00
LICENSE Initial Linux packages build rools for CPack. 2014-01-21 20:34:36 +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.