Open Source Computer Vision Library
Go to file
Ricardo Ribalda Delgado 6fc5697950 ocl: Fix OpenCL library detection in Linux
OpenCL runtime does not require OpenCL development file (libOpenCL.so),
just the "run" library (so.1).

This patch searches for the run library (so.1) if the dev library (.so)
is not found.

Web search shows that this error has been present since at least 2015
http://answers.opencv.org/question/80532/haveopencl-return-false/

Signed-off-by: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
2017-08-23 16:38:06 +02:00
.github migration: github.com/opencv/opencv 2016-07-12 12:51:12 +03:00
3rdparty cmake: disable HAVE_POSIX_SEMAPHORES on Apple platform 2017-08-14 17:19:51 +03:00
apps trace: initial support for code trace 2017-06-26 17:07:13 +03:00
cmake cmake: CMP0026 NEW 2017-08-19 15:15:05 +00:00
data fixing models to resolve XML violation issue 2017-06-13 09:42:15 +02:00
doc Merge pull request #9382 from StevenPuttemans:fix_9121 2017-08-16 13:56:33 +00:00
include Merge pull request #7370 from souch55:Fixxn 2016-10-01 10:44:56 +00:00
modules ocl: Fix OpenCL library detection in Linux 2017-08-23 16:38:06 +02:00
platforms OpenCV version++ 2017-08-03 23:58:23 +00:00
samples Merge pull request #9049 from Cartucho:improve_mask_tutorial_codes 2017-08-21 07:14:46 +00:00
.gitattributes build: added VERSIONINFO resource 2017-06-20 15:45:21 +03:00
.gitignore .gitignore: added ".cache" directory back 2017-06-21 19:03:17 +03:00
.tgitconfig Add tgit.icon project config 2014-02-26 17:46:52 +08:00
CMakeLists.txt cmake: CMP0026 NEW 2017-08-19 15:15: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.