Intel® Distribution of OpenVINO™ Toolkit
Community assistance about the Intel® Distribution of OpenVINO™ toolkit, OpenCV, and all aspects of computer vision-related on Intel® platforms.
6254 Discussions

Trouble using OpenVINO with Visual Studio 2017 (building 2019_R1)

Nicolas6
Beginner
544 Views

Hello,

 

OpenVINO version : openvino_2022.1.0.643

OS : Windows Version 10.0.19044 Build 19044

 

I want to use the OpenVINO runtime engine in a C++ application which is configured for Visual Studio 2017. The problem is that OpenVINO 2022.1 (the latest version) is only configured for Visual Studio 2019.

I still tried to build using 2022.1 but I obviously get errors which are similar to those :

E1696	Cannot open source file "ie_plugin_config.hpp" C:\Program Files (x86)\Intel\openvino_2022\runtime\include\openvino\runtime\core.hpp 18
E1696	Cannot open source file "ie_precision.hpp" C:\Program Files (x86)\Intel\openvino_2022\runtime\include\openvino\runtime\properties.hpp 19
E0145	Cannot initalize member "ov::AttributeVisitor::invalid_node_id" C:\Program Files (x86)\Intel\openvino_2022\runtime\include\openvino\core\attribute_visitor.hpp 120
E0145	Cannot initalize member "ov::Interval::s_max" C:\Program Files (x86)\Intel\openvino_2022\runtime\include\openvino\core\interval.hpp	109
E0145	Cannot initalize member "ov::float16::frac_size" C:\Program Files (x86)\Intel\openvino_2022\runtime\include\openvino\core\type\float16.hpp 23
E0145	Cannot initalize member "ov::float16::exp_size" C:\Program Files (x86)\Intel\openvino_2022\runtime\include\openvino\core\type\float16.hpp 24
E0145	Cannot initalize member "ov::float16::exp_bias" C:\Program Files (x86)\Intel\openvino_2022\runtime\include\openvino\core\type\float16.hpp 25
C1083	Cannot open include file: 'ie_plugin_config.hpp': No such file or directory (compilation of source file ../../source_file.cpp) c:\program files (x86)\intel\openvino_2022\runtime\include\openvino\runtime\core.hpp	18

I have already used OpenVINO runtime in a very simple C++ application to check if my installation works, this time using Visual Studio 2019. Everything works fine.

 

First thing to say is that upgrading the initial C++ application to a Visual Studio 2019 project cannot be done.

 

So I tried to find a version of OpenVINO that works for Visual Studio 2017. I found out that OpenVINO 2019_R1 works on Visual Studio 2017 (https://github.com/openvinotoolkit/openvino/tree/2019_R1/inference-engine), but the installer isn't available anymore on Intel's website (https://www.intel.com/content/www/us/en/developer/tools/openvino-toolkit/download-previous-versions.html?operatingsystem=window&distributions=webdownload&version=2019%20Update%201%20Eng/Jpn&options=online)

 

So I tried to build from source, cloning the 2019_R1 tag from github and following the build instructions, but the project needs Intel C++ Compiler 18.0 which can't be found anymore.

 

My questions are :

- Is there a easier way to make OpenVINO Runtime work for Visual Studio 2017 ?

- If not, is there a way to get access to a 2019_R1 version of OpenVINO ?

       - Is the Inference Engine the same thing as Runtime ?

- If not, what are my other options ?

 

Thank you,

Nicolas

 

 

0 Kudos
4 Replies
Peh_Intel
Moderator
514 Views

Hi Nicolas,


Thanks for reaching out to us.


According to documentation, OpenVINO™ Toolkit version 2020.3 is supported by Microsoft Visual Studio with C++ 2019, 2017, or 2015 with MSBuild.


This installer is still available on download page:

https://www.intel.com/content/www/us/en/developer/tools/openvino-toolkit/download-previous-versions.html?operatingsystem=window&distributions=webdownload&version=2020%203.2%20LTS&options=online



Regards,

Peh


0 Kudos
Nicolas6
Beginner
480 Views

Hi Peh,

 

Thank you, everything worked fine.

 

I have another question, is it easy to compile OpenVINO Runtime into a dll ?

 

Nicolas

0 Kudos
Peh_Intel
Moderator
442 Views

Hi Nicolas,


Glad to hear you are doing well.


Compiling OpenVINO runtime into a .dll is not straightforward and not easy but it is doable. The idea to do so can refer to this GitHub discussion.

 

 

Regards,

Peh


0 Kudos
Peh_Intel
Moderator
401 Views

Hi Nicolas,


This thread will no longer be monitored since we have provided a solution and answer. If you need any additional information from Intel, please submit a new question. 



Regards,

Peh


0 Kudos
Reply