![]() sln) as a “source” since it involves adding/removing source files, modifying library dependencies, setting build dependencies etc. These need not (and should not) be checked into the source repository as sometimes they are large and user specific.Ī Visual Studio developer might consider the project file (. obj, Visual Studio produces many more transient files like. Other than the typical intermediate files like. A build will always generate a lot of temporary/intermediate files and to avoid polluting the actual source, it is recommended to have out of source builds. Anything that is or can be consistently generated from the source files should be considered as output of the build process. Typically source should be considered as any files that are explicitly modified by the developer. Continuing from the preface CMake for Visual Studio Developers. Most references here is based on Visual Studio 2010 but will apply equally well to other versions. It is primarily intended for a C++ developer using Visual Studio. This post will map CMake commands to the Visual Studio IDE with an example which makes learning much easier. CMake produces Visual Studio solutions seamlessly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |