Any configuration hange made outside CMake will be unsafe, because it will be local and probably deleted when CMake is run again. NOTE: It is important to understand that when using CMake, we are placing it “in charge” of the project configuration, that means that every change to the project configuration should be done in CMake and not in the IDE (for example) anymore. We can dictate the project structure in a platform-agnostic manner, so whoever downloads our code can generate the solution project files as we initially planned, regardless of the chosen environment.ĬMake real job is configuring and using the Native Build Tool (the set of IDE+compiler environment), depending on some platform-agnostic instructions given by the programmer.
By using it we are not tied anymore to a specific IDE environment, like Visual Studio (or a specific version of it), or NetBeans, or CLion, because the project files are going to be independently generated using CMake. Riccardo Loggini CMake in Visual Studio Table of ContentsĬMake is a tool that allows us to generate project files from our code for a multitude of different environments.
0 kommentar(er)
