Revision history [back]

I´m not such a programming authority to give answers with why some things work or don´t, but there apparently are some serious omissions in the https://docs.opencv.org/3.4/dd/d6e/tutorial_windows_visual_studio_opencv.html, at least for VS 2017.

Quick shot: What helps: 2 different PropertySheet.props One for Debug with Linker > Input > Additional Dependencies > opencv_world341d.lib (with the d for debug in it) and for Release with opencv_world341.lib

Hope that helps G.

I´m Edit and additions in response to @LBerger 's comment:
~~I´m not such a programming authority to give answers with why some things work or don´t, but there apparently are some serious omissions in the https://docs.opencv.org/3.4/dd/d6e/tutorial_windows_visual_studio_opencv.html, Win-VS-tutorial, at least for VS 2017.2017.~~ (strike-through s element seems to work, but not tildes?)

More carefully phrased with enough time on hand with the proposed solution (below) already out:
I found the Win-VS-tutorial very helpful, but though I´ve done a lot of programming for decades, I´m no expert in OpenCV and C++ and VS and all their variants and dependencies, so the below was not the only pit, even in this tiny sample and reading carefully.

(I had tried to get VisionWorks with OpenCV running on Windoze (with the Jetson in mind), but took the step back because of all the "moving parts" overwhelming me.)

Quick shot: shot:
What helps: 2 different PropertySheet.props PropertySheet.props
One for Debug with Linker > Input > Additional Dependencies > opencv_world341d.lib (with the d for debug in it) and for Release with opencv_world341.lib

Hope that helps helps
G.