We also have Global Properties that will be applied by default to every target we define, such as set(CMAKE_CXX_STANDARD 11) that will tell CMake to look for a C++11 compiler version.
Targets have Properties: the source files a target is built from, the compiler options it requires, the libraries it links against. Our Application is build as a collection of Targets that depend on and use each other. By default, in Visual Studio Solution they will correspond to a Project each. Targets model the components of our application: an executable is a target, a library is a target. The fundamental objective in CMake is defining a list of Targets and defining Properties in them. CMake offers a multitude of tools which are much more in number than the ones described in this article, many of which goes beyond the scope of a base environment setup.
The scope of this article is giving a basic but complete understanding of the CMake tool, with a focus on Visual Studio environment, in order to set up a fairly simple project. To check a practical usage of CMake you can refer to my github repo FirstDX12Renderer by clicking here. At the time of writing this article, VisualStudio 2019 is using CMake 3.16. Generally we should make sure that the version of CMake that we are using got released after the compiler we are using, just to increase the chance we have all the possible updated tools at our disposal. 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.
#Cmake visual studio multi jobs code
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)
