Re: digiKam MSVC compilation problems on build.kde.org...

2020-02-16 Thread Gilles Caulier
Hannah, The linking problem with opencv-core is very common under windows. In fact .lib files path is not populated properly. Just check with google and this kind of terms: "cmake fatal error LNK1104: cannot open file 'opencv_core-NOTFOUND.obj'" There are plenty of non elegant solutions to fix i

Re: digiKam MSVC compilation problems on build.kde.org...

2020-02-15 Thread Hannah von Reth
I just spend another hour with the rotten lib opencv. Before you try anything else please patch it to use our ffmpeg and not download some random binaries. The library also installs itself to x64\vc16\bin which does not match any sane layout. On 15/02/2020 10:57, Gilles Caulier wrote: Comp

Re: digiKam MSVC compilation problems on build.kde.org...

2020-02-15 Thread Gilles Caulier
Compare side by side the build and the factory opencv detection properties : build.kde.org (working) : 01:53:02 -- OpenCV ARCH: x64 01:53:02 -- OpenCV RUNTIME: vc16 01:53:02 -- OpenCV STATIC: OFF 01:53:02 -- Found OpenCV: C:/Craft/CI-Qt514/windows-msvc2019_64-cl-debug (found version "4.1.2")

Re: digiKam MSVC compilation problems on build.kde.org...

2020-02-15 Thread Gilles Caulier
Ok, yesterday, i patch the opencv python scrip to revert back to 4.1.2 version to see if DK link better on core object : no more... 03:45:27 -- OpenCV ARCH: x64 03:45:27 -- OpenCV RUNTIME: vc15 03:45:27 -- OpenCV STATIC: OFF 03:45:27 -- Found OpenCV: C:/Craft/BinaryFactory/windows-msvc2017_64-

Re: digiKam MSVC compilation problems on build.kde.org...

2020-02-13 Thread Ben Cooksley
On Thu, Feb 13, 2020 at 11:45 PM Gilles Caulier wrote: > > Right, but the Q is : why with the CI, openCV detection work as expected? > > There is a solution to drop definitively the cmake macro in DK to > handle openCV. With 4.x, OpenCV start to deploy the library > configuration through the targe

Re: digiKam MSVC compilation problems on build.kde.org...

2020-02-13 Thread Gilles Caulier
Right, but the Q is : why with the CI, openCV detection work as expected? There is a solution to drop definitively the cmake macro in DK to handle openCV. With 4.x, OpenCV start to deploy the library configuration through the target cmake scripts which is the modern way. I tried with openCV 4.1 t

Re: digiKam MSVC compilation problems on build.kde.org...

2020-02-13 Thread Hannah von Reth
From the logs: -- OpenCV libs : opencv_core;opencv_objdetect;opencv_imgproc;opencv_imgcodecs;opencv_dnn;opencv_flann With modern cmake I'd expect absolute paths here, or at least the full names, -lfoo does not work on Windows. Also, have a look on how opencv is installed. *00:19:58.081* -- In