Add Visual Studio 2017 support
It's out of RC phase now so it would be awesome to be able to use the latest tools.
I'd do it myself but I'm not familiar with cmake stuffs on windows and how that already supports creating projects for vs 2017.
#2 Updated by Lennart Bernhardt 8 months ago
Everything does work fine, that's why this is a feature.
Basically on windows you need to generate different project files for different versions of Visual Studio. Right now there is only support for vs2013 and 2015 in the build scripts.
Adding support for vs 2017 in the build scripts would remove the need to upgrade projects.
#3 Updated by Plutonic Overkill 8 months ago
This issue doesn't really have anything to do with CMake or the build scripts, it's just that binaries from different compiler versions aren't compatible with one another, and most libraries still don't have prebuilt VS 2017 binaries (the build script uses mainly these binaries). AFAIK, OpenMW will still build on VS 2017, but you'll need to build all the dependencies yourself (a tedious process on Windows). To add proper support, these binaries would need to be hosted somewhere so they could be downloaded by the build script.
#7 Updated by Plutonic Overkill 7 months ago
Done a quick implementation and it seems to work so far. Haven't tested it yet for VS2013 or VS2015 but they should work OK.
#13 Updated by Plutonic Overkill 7 months ago
I've just come across another case that I hadn't considered before, where this feature would be useful. Whenever CMakeLists.txt is modified, CMake has to re-run, using whatever generator was specified to it the first time around. This means that if the project files were manually upgraded, they'll be regenerated, and you'll have to upgrade them again every time you change the CMakeLists.txt file.