summaryrefslogtreecommitdiffstats
path: root/meta-oe/recipes-support/opencv/opencv
Commit message (Collapse)AuthorAgeFilesLines
* Revert "opencv: disable broken Intel FP16 detection"Randy MacLeod2017-05-092-272/+0
| | | | | | | | | This reverts commit 51fbd3cf7db14399bc1c69c4a5fd63f157fd209d. The long log was truncated due to a formatting error. Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* opencv: disable broken Intel FP16 detectionRandy MacLeod2017-04-282-0/+272
| | | | | | | | | | | | | With opencv-3.2, the configuration detects if the target supports half-precision floating-point format. This fails to compile for some Intel targets such as skylake with an error such as: error: '_mm_cvtph_ps' was not declared in this scope The configuration worked in opencv-3.1 so revert two commits to drop the FP16 detection even though it may make opencv slower. The only change in the configure log is: Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* opencv: Update to version 3.2Ricardo Ribalda Delgado2017-01-104-31/+26
| | | | | | | | | -Only enable protobuf as dependency if dnn module is enabled -Download manually xfeatures from 3rd party repo -Remove uneeded fixgcc60patch Signed-off-by: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* opencv: Fix build with gcc 6.0Ricardo Ribalda Delgado2016-08-151-0/+30
| | | | | | | | It seems like gcc 6.0 does not have the same behaviour as previous 5.x with regards isystem flag. Signed-off-by: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* opencv: Use pre-downloaded ippRicardo Ribalda Delgado2016-04-121-0/+28
| | | | | | | We should not rely on cmake downloading ipp at configure time. Signed-off-by: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* opencv: Fix pkg-config file.Ricardo Ribalda Delgado2016-04-121-0/+29
| | | | | | | | | Libdir was pointing to the wrong location also fix for QA Issue: opencv.pc failed sanity test (tmpdir) in path Signed-off-by: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* opencv: backport commit to compile with ppcLukas Bulwahn2015-10-131-0/+49
| | | | | | | | | | | | | During the testing of the meta-ros layer, I discovered that opencv does not cross-compile for the ppc architecture. The error is reported in the meta-ros issue tracker #355 [1]. To address this error, this commit applies a patch that is already provided upstream in the opencv version 3.0. [1] https://github.com/bmwcarit/meta-ros/issues/355 Signed-off-by: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* opencv: Upgrade to 2.4.11mike.looijmans@topic.nl2015-03-061-44/+0
| | | | | | | | | | | | Upgrade OpenCV to the 2.4.11 release. Remove the opencv-fix-pkgconfig-generation patch which has been integrated upstream, be it in modified form. Disable 1394 support by default to get a deterministic build. Fix "jasper" dependency, the BUILD_JASPER parameter served only to build an internal library, while WITH_JASPER actually controls whether jpeg2000 support was desired. Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* opencv: fix pkg-config file generationStefan Herbrechtsmeier2012-12-191-0/+44
| | | | | | | | Replace absolute library path with library name spec and library search path option in pkg-config file. Signed-off-by: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* opencv, opencv-samples: drop 2.3.1Koen Kooi2012-07-131-37/+0
| | | | Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
* opencv: import from oe-classic and upgrade to 2.3.1Connor Abbott2011-11-011-0/+37
OpenCV <= 2.2 won't compile on oe-core due to the lack of v4l1 headers, and therefore wasn't included in this patch. Also, the support for newer cv2-style python bindings is a bit hacked up at the moment due to the way OpenCV detects the Python version and Numpy headers (see 0001-Fix-CMakeLists.txt-numpy-detection.patch). In particular, it requires the native & target python to be the same version and have similar site-packages directories, which is true at least for now in OE. Signed-off-by: Connor Abbott <cwabbott0@gmail.com> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>