vc150 or vc141?

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   Hi, 
I am compiling for VS 2017. All output files/directories are called something with "vc150" - but platform toolset for VS 2017 is vc141. This causes problem for us as we use the toolset version in post build steps, etc. 

Another problem I have is that I need to compile the libraries for VS 2015 but only have VS 2017 installed. This is no problem as I can change easily change ploatform toolset in properties to vc140. However, all the output files/directory are called something with *vc150*...

I would suggest using $(PlatformToolset) in out file names/directories: 

e.g.:
ToolkitPro1830$(PlatformToolset)$(Platform)UD  (for Unicode Debug, vc141x64 and vc141Win32)

or does it require at least a semi-modern version of Visual Studio? 

Thanks.

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
Fredrik Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 22 June 2005 Status: Offline Points: 235	Post Options Post Reply Quote Fredrik Report Post Thanks(0) Quote Reply Topic: vc150 or vc141? Posted: 20 February 2018 at 10:08am
	Hi, I am compiling for VS 2017. All output files/directories are called something with "vc150" - but platform toolset for VS 2017 is vc141. This causes problem for us as we use the toolset version in post build steps, etc. Another problem I have is that I need to compile the libraries for VS 2015 but only have VS 2017 installed. This is no problem as I can change easily change ploatform toolset in properties to vc140. However, all the output files/directory are called something with vc150... I would suggest using $(PlatformToolset) in out file names/directories: e.g.: ToolkitPro1830$(PlatformToolset)$(Platform)UD (for Unicode Debug, vc141x64 and vc141Win32) or does it require at least a semi-modern version of Visual Studio? Thanks.
	Windows 10, Visual Studio 20157, Toolkit Pro 18.3.0