Go to file
Sergiu Deitsch d71ec0cd1d cmake: support OPTIONAL_COMPONENTS in OpenCVConfig.cmake
find_package allows to specify optional components. This way, the
command will not fail if any of the components marked as optional was
not found. This is useful in cases where components such as xfeatures2d,
viz etc. are not available either because they were not compiled by the
user or package maintainers decided to not provide the packages at all.

The user can check the availability of the optional component using the
OpenCV_<component>_FOUND variable.
2016-12-19 00:15:51 +03:00
.github migration: github.com/opencv/opencv 2016-07-12 12:51:12 +03:00
3rdparty cmake: unpack IPPICV into binary directory 2016-12-16 18:43:54 +03:00
apps update samples: waitKey() usage 2016-12-15 15:39:47 +03:00
cmake cmake: support OPTIONAL_COMPONENTS in OpenCVConfig.cmake 2016-12-19 00:15:51 +03:00
data Removing whitespace to appease doc builder 2016-08-12 00:31:50 -03:00
doc Merge pull request #7866 from alalek:update_waitKey 2016-12-16 12:25:11 +00:00
include Merge pull request #7370 from souch55:Fixxn 2016-10-01 10:44:56 +00:00
modules don't run OpenVX pyrLK if user asked for err vector 2016-12-16 23:38:47 +03:00
platforms cmake: ARM toolchain: find ld/ar 2016-11-10 18:00:32 +03:00
samples bug fix for #7846 2016-12-17 21:48:29 +08:00
.gitattributes
.gitignore Improved thrust interop tutorial. 2015-09-24 09:32:38 -04:00
.tgitconfig Add tgit.icon project config 2014-02-26 17:46:52 +08:00
CMakeLists.txt Merge pull request #7769 from alalek:cmake_ffmpeg_cleanup 2016-12-01 20:24:05 +00:00
CONTRIBUTING.md migration: github.com/opencv/opencv 2016-07-12 12:51:12 +03:00
LICENSE Update license year range to 2016 2016-01-18 10:11:01 +05:30
README.md migration: github.com/opencv/opencv 2016-07-12 12:51:12 +03:00

OpenCV: Open Source Computer Vision Library

Resources

Contributing

Please read before starting work on a pull request: https://github.com/opencv/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.