CMAKE CONFIGURE GENERATOR
If no generator is found, CMake Tools produces an error.ĬMake Tools has a variety of locations where configuration options can be defined.Automatically generated Visual Studio kits set this attribute to the Visual Studio generator matching their version. The kit's preferredGenerator attribute.The list has a reasonable default that works for most environments. Each element in this list is checked for validity, and if one matches, it is chosen. The config setting cmake.preferredGenerators.Instead, it tries to detect a preferred generator from a variety of sources, stopping when it finds a valid generator. See Kit options for more information about the different types of kits.ĬMake Tools tries not to let CMake decide implicitly which generator to use. See CMake kits for more information about how kits work. A kit may also define a preferredGenerator. When CMake Tools runs the configure step, it takes the following into consideration:ĬMake kits provide information about the toolchains available on your system that can be used with CMake to build your projects.įor toolchain, CMake Tools sets the CMake cache variable CMAKE_TOOLCHAIN_FILE to the path to the file specified by the kit.įor compilers, CMake Tools sets the CMAKE_COMPILER cache variable to point to the path for each defined in the kit.įor Visual Studio, CMake Tools sets environment variables necessary to use the selected Visual Studio installation, and sets CC and CXX to cl.exe so that CMake will detect the Visual C++ compiler as the primary compiler, even if other compilers like GCC are present on $Path.Įach kit may also define additional cache variable settings required for the kit to operate. The CMake Tools configure stepĬMake Tools drives CMake via the cmake-file-api which provides project info via a file on disk. If you are building from within Visual Studio Code, we recommend you use the Ninja build tool. Regardless of generator, CMake Tools always supports building from within Visual Studio Code. There are many different Visual Studio generators, so it is recommended to let CMake Tools automatically determine the appropriate generator. See cmake.preferredGenerators.Įmits a Makefile for the project that can be built via make.Įmits visual studio solutions and project files. This is the generator CMake Tools tries first, unless configured otherwise. There are several families of generators available: GeneratorĮmits files for the Ninja build tool. The Generator tells CMake what kind of tool will be used to compile and generate the results of the build. The result of a configure depends on the CMake Generator. Unless overwritten or deleted, values in the CMake Cache persist between CMake runs.ĬMake doesn't do the build itself, it relies on build tools installed on your system.
(CMake Tools doesn't use CMake's -C argument).
On the CMake command line, these appear as -D arguments. These allow you to control the build settings.
0 kommentar(er)
