- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am attempting to use the ipp_custom_library_tool_gui.exe with V2017 Update 3. The release notes indicated support for VS2017 and the installer said it was integrating with that version of VS, but the custom library tool does not seem to be ready to use VS2017.
The Options menu does not list VS2017 as an option. Choosing VS2015 fails compilation (I don't have VS2015 installed, so no real surprise there). It does still work with my VS2013 install but I was hoping to finally move all of my libraries up to VS2017.
Is this an oversight or am I doing something wrong?
Thanks, Matt
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you for reporting the issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Matthew
As a workaround you can save build script in the tool instead of automatic build, then start VS 2017 command prompt for appropriate architecture and run build script from there. There is no actual dependency on particular version of Visual Studio, it just need to know there to find compiler tools.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Pavel V. (Intel) wrote:
As a workaround you can save build script in the tool instead of automatic build, then start VS 2017 command prompt for appropriate architecture and run build script from there. There is no actual dependency on particular version of Visual Studio, it just need to know there to find compiler tools.
I will give that a shot. Thanks, Matt
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page