Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VC2019 / Visual Studio project configs for v142 compiler toolset #2113

wants to merge 2 commits into
base: master


Copy link

commented Jul 6, 2019

As discussed in #2082, skipping VC2017 folders since Visual Studio 2019 / v142 is stable, freely available, and in my opinion much better than Visual Studio 2017 (and 2015).

@richardeakin richardeakin added the msw label Jul 6, 2019


This comment has been minimized.

Copy link

commented Jul 10, 2019

Agree, also vs2019 compiles faster than vs2015.


This comment has been minimized.

Copy link

commented Jul 22, 2019

I would suggest we skip the vs project *.vxcprojt totally, since current cmake system works fine on Windows and it's cross platform.
VS2019 also has direct cmake support.


This comment has been minimized.

Copy link
Collaborator Author

commented Jul 24, 2019

@fei4xu we may think about that some time in the future, but up until now (and currently), very few Windows users are building via cmake - they all depend on the included VS project files, so we'll continue to supply them until that changes. A large part of this decision is that cmake-generated visual studio project files are difficult to hand tune, and are generally setup pretty poor compared to those we make by hand.

Using cmake directly in Visual Studio is interesting, although my attempts to use it have shown that it is still quite experimental, especially with more complex project structures.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
3 participants
You can’t perform that action at this time.