Chiebot-Mirror
/
opencv
8
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Open Source Computer Vision Library https://opencv.org/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
9962 Commits
6 Branches
128 Tags
3.0 GiB
 
 
 
 
 
 
Tag: Branch: Tree: 2e393ab833
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '2e393ab833'
${ noResults }
Go to file
Vicente Olivert Riera 2e393ab833
superres: Fix return value VideoFrameSource_GPU 		11 years ago
3rdparty Android native camera rebuilt after sources update. 11 years ago
apps Fixes for QNX 6.6 Neitrino support. 11 years ago
cmake Merge pull request #3363 from asmorkalov:qnx_support 11 years ago
data fixed two models, adding xml identifier to correct position 11 years ago
doc OpenCV Manager version++. 11 years ago
include All installed files marked with component names for install customization. 11 years ago
modules superres: Fix return value VideoFrameSource_GPU 11 years ago
platforms Merge pull request #3363 from asmorkalov:qnx_support 11 years ago
samples Merge pull request #2965 from soulslicer:patch-2 11 years ago
.gitattributes Added more text/binary/whitespace attributes for files we have. 12 years ago
.gitignore updated .gitignore 11 years ago
.tgitconfig Add tgit.icon project config 11 years ago
CMakeLists.txt Merge pull request #3363 from asmorkalov:qnx_support 11 years ago
LICENSE Initial Linux packages build rools for CPack. 11 years ago
README.md Replaced Gittip button 11 years ago
index.rst android -> plarforms/android 12 years ago

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.