Support #5594
closedwt4 build using VS 2017 RTM?
0%
Description
I've been using Wt 3.3.6 with VS2015. CMake ran once, created vcxproj files, which I then customized for my situation. Got new computer, reinstalled everything, CMake wanted to change my vcxproj files back to the original state.
Just installed VS2017 RTM, which is supposed to have more complete support for CMake projects. I figure that I should jump to Wt4, and I'm hoping that I can avoid the problems described in the 1st paragraph by customizing the CMake files themselves.
I either want to remove any dependency on CMake OR remove any dependency on vcxproj files for Wt builds.
Any help or advice would be greatly appreciated. Does anyone have step-by-step procedure for building Wt4 with VS2017?
Updated by Roel Standaert about 7 years ago
We haven't gotten around to checking out Visual Studio 2017 yet. I will first make sure that Wt 3.3.7 gets built with Visual Studio 2017.
Updated by Roel Standaert about 7 years ago
Seems like we don't actually need binary builds for VS2017, because 2015 and 2017 are binary compatible for a change.
Updated by Gunnar Skogsholm about 7 years ago
We need to build our own binaries. A step-by-step procedure to build wt4 with VS 2017 is needed.
Updated by Wim Dumon about 7 years ago
Hey Gunnar,
I've used 2017 preview releases to build Wt, using the traditional approach (so not with the integrated cmake support), and this works fine. I have no experience with the cmake integration of VS2017. However, I have doubts if the issue of combining manual changes and using cmake to generate .proj files will be resolved using that integration?
Best regards,
Wim.
Updated by Gunnar Skogsholm almost 7 years ago
I have succeeded in building Wt4 with VS2017. All is well, this can be closed.