Running VS2017 with Parallel Studio XE installed, if I change from the MS C++ compiler, to the Intel Compiler, and then back to the MS compiler, the platform toolset is changed from v141_xp to v141
Surely you should restore it to the original setting, rather than setting it to the default.
With this problem in mind, does the Intel compiler support a Windows XP target, if so how should that be specified?
Thanks for reporting this to us.
This is a known limitation as mentioned Intel C++ 19.0 compiler release notes for Windows.(https://software.intel.com/content/www/us/en/develop/articles/intel-c-compiler-190-for-windows-relea...)
You can check in the Known limitations section.
Could you please tell us which version of the Intel C++ compiler you were using?
This issue only happens on Windows XP, and since we do no support Windows XP, the fix cannot be provided.
If your query has been answered please confirm so we can close the thread.
Hardly - this is a Windows 10 X64 system. Not Windows XP.
If you are saying you won't support a target on XP that's OK, but you should restore the status quo when the user switches back to use the MS compiler. So I believe you still have a bug that should be fixed.
Sorry for the miscommunication.
What I meant to say was this issue only happens when the target was Windows XP, and Windows XP is no longer supported.
For all other targets, the platform toolset value won't be changed when you switch compilers.
You're missing the point - if the project is set to use the Windows XP (v141_xp) toolset under VS2017 and I switch to the Intel compiler, I can accept that because you don't support that target that you change to the standard V141 toolset. No problem with that in principle, but you really should issue a warning that you have done so.
My gripe is that if I then switch back to the MS compiler, you DON'T restore the toolset back to Windows XP (v141_xp) - that is plain BAD behaviour.
Hmmm I sort of see your point - but that's not how it works :(!
Can you at least change things so that if you do change this sort of thing if future that you issue a warning?
Thanks for the suggestion
We will consider that and plan to issue a warning in future once we receive enough requests.
If you are satisfied please confirm so we can close this thread.
Thanks and Regards
Thanks for the confirmation.
We are closing this thread. If you require additional assistance from Intel, please start a new thread. Any further interaction in this thread will be considered community only.