- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is OpenVINO Toolkit compatible with Visual Studio 2017?
Can I use VS2017 instead of 2015?
I couldn't find any clear information about it.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Ozturk Kusat,
OpenVINO samples does not support VS 2017 yet.
It supports VS 2015 Pro, and Community version also.
Regards,
Peter.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you for your response,
I wonder that if it will support VS 2017 in the future? If yes, When?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Ozturk Kusat,
OpenVINO R2 version is just released.
It supports VS 2017 pro and community version.
Please try it.
Regards,
Peter.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Peter,
It's good to know OpenVINO R2 is released.
When I download OpenVINO R2 and follow the "Installing the OpenVINO™ Toolkit for Windows* 10", then type "demo_squeezenet_download_convert_run.bat" command. The compiler report error when it's trying to compile for Samples.sln.
There is the error : (Sorry for some Chinese character in it)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Lee,
do you have Release x64 enable in Visual Studio 2017? Are you able to build the samples and open them in Visual Studio 2017?
You will find the script
create_msvc2017_solution
to build them under C:\Intel\computer_vision_sdk_2018.2.299\inference_engine\samples
Then, in the folder build2017, you can open the VS solution and see if Release x64 is enabled for you and if you can compile them.
Best,
Severine
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Severine,
Thanks for the reply.
I add "/p:Platform="x64"" in the batch file, then the issue can be fixed.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page