Chiebot-Mirror
/
opencv
mirror of https://github.com/opencv/opencv.git
8
0
Fork 0
Code Issues 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.
10087 Commits
6 Branches
126 Tags
3.0 GiB
 
 
 
 
 
 
Tag: Branch: Tree: 8548a8430e
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '8548a8430e'
${ noResults }
Go to file
StevenPuttemans 8548a8430e
fixing wrong model sizes 		10 years ago
3rdparty Full AARCH64 support with NEON and new CUDA toolkit. 10 years ago
apps Fixes for QNX 6.6 Neitrino support. 10 years ago
cmake Fixed samples install permissions for Debian packaging. 10 years ago
data fixing wrong model sizes 10 years ago
doc fixing tutorial errors 10 years ago
include All installed files marked with component names for install customization. 11 years ago
modules Merge pull request #3587 from vpradeep07:fix/pnpransac_race_cond 10 years ago
platforms Update link to information about Android platform. 10 years ago
samples remove an unused #endif 10 years ago
.gitattributes Added more text/binary/whitespace attributes for files we have. 11 years ago
.gitignore updated .gitignore 11 years ago
.tgitconfig Add tgit.icon project config 11 years ago
CMakeLists.txt opencv_testing.sh script installation is removed as run tests script does the same thing. 10 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.