

I've also consulted Microsoft's docs on using CMake in Visual Studio, which seems to indicate that for a CMake project, the. That question and most of the answers seem to assume that everyone will be using VS, which is not the case here. (My emphasis.) This isn't really that the intent is actually to use CMake to create the build system, one of which could be Visual Studio. There is this question which asks about which Visual C++ file types should be checked in for a Visual C++ project.

If it's a built artifact, it should NOT go into version control.It is required to be there for other reasons (e.g.It is required to build one or more artifacts (including docs, source code, graphics).The criteria I typically use for deciding whether things belong in version control: gitignore file or more generally excluded from version control. Some of these files appear to contain things like paths that seem likely to be unique to that particular person's particular computer, which prompted the question about whether these should be added to the projects. vcxproj.filters files strewn about in nearly every directory. Recently, I noticed that a Windows developer on one of the projects checked in.

Many of these projects are intended to be cross-platform, most often running on either Linux (my natural habitat) or Windows and generally relying on CMake to build. I work on a number of code projects, some open source and some not.
