you really can’t ? (hard to believe…)
there is no error here at all, only INFO messages
(it tries to load some plugins, that do not exist on your machine)
there wont be any such messages in RELEASE mode
however, if you would have a gtk (or qt) based highgui plugin dll, you could choose that as backend at runtime
I understand that waitKey(0) will block until I press the key.
But only in case of Debug/x64, there is no the 2nd imshow(), instead it will exit with error code:
In fact it throw except:
Exception thrown at 0x00007FFC380E5A26 (opencv_world453d.dll) in SUW1.exe: 0xC0000005: Access violation reading location 0x0000000000000010.
However for release/x64, there is no problem.
For 32bit there is no problem for both debug and release dll.
I am sure it is not a bug in my code, but I suspect there is a need to set some flag etc in Debug/x64
I use VS2019, version 16.10.4. and use vc15.
The Platform toolset in VS is Visual Studio 2019 (V142)
We want to use a clean and new laptop to install VS 2019 and the latest OpenCV to see if these are sufficient to start the programming in C++ with OpenCV
I only installed these 2 days ago. And I did not install anything else except python Opencv 3.7 which is working perfectly.
My old laptop has multiple OpenCV libraries, some are locally built, some are downloaded from release 3.5 onwards.
We never experienced such inconsistencies between Debug and Release versions.
I am thinking to build a local opencv or download an old version to see if there is a problem.
I build both debug and release version of OpenCV, using my VS2019.
I have the exact result as I use the dlls downloaded.
For release version, it can run the second imshow() without problem.
For debug version, it shows the first image, but with a lot of “info” and then exit with error code.
Since this debug info is an option, I will try to unchecked it and build a debug version soon.
I’m running openCV 4.5.5, vs2017, VC15, and face the exact same behaviour. Images run properly when building vs2017, but in vs2017_debug I get only first image. @qceptliujun did you move forward on this topic ?