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.
8698 Commits
7 Branches
126 Tags
3.0 GiB
 
 
 
 
 
 
Tag: Branch: Tree: bbece095fb
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'bbece095fb'
${ noResults }
Go to file
hbristow bbece095fb
Starting writing Matlab testing framework 		12 years ago
3rdparty Merge remote-tracking branch 'origin/2.4' 12 years ago
android Build fixes. Build scrips reorganized. 12 years ago
apps Merge remote-tracking branch 'origin/2.4' 12 years ago
cmake Starting writing Matlab testing framework 12 years ago
data Merge release 2.4.4 12 years ago
doc fixed documentation build 12 years ago
include Minimize usages of legacy C API inside the library 12 years ago
ios enabled png and jpeg for iOS 12 years ago
modules Starting writing Matlab testing framework 12 years ago
platforms Merge remote-tracking branch 'origin/2.4' 12 years ago
samples Preparing to rebase 12 years ago
.gitattributes Fix typo in .gitattributes. 12 years ago
.gitignore Changed the file .gitignore 12 years ago
CMakeLists.txt cmake now attempts to generate and compile a simple mex file at configure time and reports the working status of the generator and compiler, rather than just naively saying Matlab exists 12 years ago
README Replace the pull request guidelines with a link to the wiki. 12 years ago
index.rst android -> plarforms/android 12 years ago

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.