Nvidia 2070 Super supported for OpenCL?

[bryan at gillson.net]

Hi Gilles, back in October I reported an issue with OpenCV that was tracked to an upstream dependency in vcpkg.

Has the change you referenced below been made in 8.9.0, and if so, is 8.9.0 stable enough for testing on a production photo library? Please let me know if there is a bug I could track instead; I did check but did not find one.

Thank you!

>> > Under Windows we package with an older release of OpenCV framework in
>> > charge of to deal and to use the GPU for the computation. This is
>> > probably the problem. This is due to a UPSTREAM bug in the VCPKG
>> > package manager.
>>
>> Thanks Gilles. Is this something I can manually correct?
>>
>> I've downloaded the latest OpenCV (v4.12) but it now deploys with only the unified opencv_world412.dll and not
>> the individual opencv_core4*.dll, opencv_imgcodecs4*.dll, etc. that digiKam bundles. Consequently, it doesn't
>>look like I can just copy the updated .dlls to the digiKam directory.

> No you cannot. openCV must be compiled with the right open trough
> VCPKG installer and digiKam must be recompiled and linked with it.
> This is a huge task that I do in a Windows 10 VM with all the
> necessary dependencies.
>
> https://vcpkg.io/en/
>
> I plan to do a huge update of the VM for the next 8.9.0 in the next
> few weeks. This is a very long task to compile all components, usually
> between 1 and 2 days. When it's done, the packaging can be easily
> processed in 30 mins and updated quickly.
>
> Please be patient, you will be able to test with a new Windows
> pre-release 8.9.0 asap.




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20251205/8539b1ce/attachment.htm>