FS#6570 - Add Visual Studio 2017 solution and projects

Attached to Project: OpenTTD
Opened by Markus Hartung (harre) - Sunday, 28 May 2017, 20:32 GMT
Last edited by frosch (frosch) - Friday, 23 June 2017, 14:27 GMT
Type Patch
Category Core
Status Closed
Assigned To No-one
Operating System All
Severity Low
Priority Normal
Reported Version trunk
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No
This task depends upon

Closed by  frosch (frosch)
Friday, 23 June 2017, 14:27 GMT
Reason for closing:  Won't implement
Comment by frosch (frosch) - Thursday, 22 June 2017, 18:39 GMT
Apparently the only difference in the project files from MSVC2015 to MSVC2017 are:
* "ToolsVersion": "14.0" -> "15.0"
* "PlatformToolset": "v140" -> "v141"
* Addition of "WindowsTargetPlatformVersion" with value "10.0.15063.0", which looks dubious to me.

Are the new project files even needed? Don't the MSVC2015 files just work?

Either way:
* I think the project files are supposed to be named "150", matching the internal version number of MSVC.
* The generation scripts "generate" and "generate.vbs" together with all the ".in" and ".filters" files need to be adjusted.
Comment by Markus Hartung (harre) - Friday, 23 June 2017, 00:07 GMT
Yeah, it seems that I'm able to get it working with just using the openttd_vs140.sln

I were just missing the proper include folders and import folders.

We can close this bug.
Comment by Patric Stout (TrueBrain) - Saturday, 23 September 2017, 23:00 GMT
With a recent patch from LordAro adding FALLTHROUGH to OpenTTD, VS2017 is yelling it needs to be in /std:c++latest. Possibly it is a good moment to introduce project files for VS2017, as then it can be changed on Project level (instead of individual).
Comment by frosch (frosch) - Sunday, 24 September 2017, 16:01 GMT
I added MSVC2017 to "generate" and "generate.vbs".
The project files differ from MSVC2015 in
* ToolsVersion 14.0 -> 15.0
* PlatformToolset v140 -> v141
* AdditionalOptions now contains /std:c++latest