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.
7670 Commits
7 Branches
126 Tags
3.0 GiB
 
 
 
 
 
 
Tag: Branch: Tree: 639450efdc
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '639450efdc'
${ noResults }
Go to file
Philippe FOUBERT 639450efdc
PvAPI support on Windows with MinGW (PR #1038 applied to the branch 2.4) 		12 years ago
3rdparty Fix build warnings from gcc 4.8 12 years ago
android Fix build problems on MIPS and Linaro NDK. 12 years ago
apps Replaced most of the usages of parallel_for with that of parallel_for_. 12 years ago
cmake PvAPI support on Windows with MinGW (PR #1038 applied to the branch 2.4) 12 years ago
data Added smile detector 12 years ago
doc Fix bug with indices 12 years ago
include Normalize line endings and whitespace 12 years ago
ios enabled png and jpeg for iOS 12 years ago
modules PvAPI support on Windows with MinGW (PR #1038 applied to the branch 2.4) 12 years ago
platforms Fix build problems on MIPS and Linaro NDK. 12 years ago
samples Fixes bug #3071. 12 years ago
.gitattributes Fix typo in .gitattributes. 12 years ago
.gitignore Changed the file .gitignore 12 years ago
CMakeLists.txt Merge pull request #929 from dominikrose:mingw-libdc1394-2-windows 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.