mirror/opencv
1
0
Fork 0
mirror of https://github.com/opencv/opencv.git synced 2024-11-27 20:50:25 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
Open Source Computer Vision Library
26,821 Commits 6 Branches 126 Tags 3 GiB
C++ 87%
C 3.4%
Python 2.8%
CMake 2.1%
Java 1.6%
Other 2.9%
70cbc3d883
Go to file
Niklas Hambüchen 70cbc3d883 cvdef.h: Don't use C's limits.h under C++ 
Just like with the other headers in the rest of the file.

See e.g. https://stackoverflow.com/questions/36831465/what-difference-does-it-make-when-i-include-limits-or-limits-h-in-my-c-cod
for the reasons, the most important one being that limits.h does not respect
namespaces, which can make problems for downstream consumers of cvdef.h.
2020-01-29 16:41:31 +01:00
.github
3rdparty cmake: reuse OpenCV NEON detection in carotene 2020-01-24 16:42:56 +03:00
apps Fix spelling typos 2019-12-27 12:46:53 +00:00
cmake core:vsx fix inline asm constraints 2020-01-28 15:48:00 +02:00
data Some mist. typo fixes 2018-02-07 06:59:15 -05:00
doc Merge pull request #16276 from themechanicalcoder:video-tutorial 2020-01-12 11:34:59 +03:00
include add missing DNN header to opencv2/opencv.hpp 2018-02-15 15:59:14 +01:00
modules cvdef.h: Don't use C's limits.h under C++ 2020-01-29 16:41:31 +01:00
platforms feat(android): add support for android modules selection 2020-01-22 19:14:34 +03:00
samples Merge pull request #16223 from l-bat:lip_jppnet 2020-01-27 19:17:43 +00:00
.editorconfig add .editorconfig 2018-10-11 17:57:51 +00:00
.gitattributes cmake: generate and install ffmpeg-download.ps1 2018-06-09 13:19:48 +03:00
.gitignore Merge pull request #15503 from cancerberoSgx:js-test-puppeteer 2019-11-17 00:29:38 +03:00
CMakeLists.txt cmake: reuse OpenCV NEON detection in carotene 2020-01-24 16:42:56 +03:00
CONTRIBUTING.md
LICENSE copyright: 2020 2020-01-02 11:58:20 +00:00
README.md

README.md

OpenCV: Open Source Computer Vision Library

Resources

Contributing

Please read the contribution guidelines before starting work on a pull request.

Summary of the 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.