\nStructure<\/a>
\nSettings<\/a>
\nManaging Targets<\/a>
\nUnderlying Build Tools<\/a>
\nDebugging CMake Scripts<\/a>
\nTroubleshooting Build Problems<\/a>
\nCustomizing Solution Explorer View<\/a>
\nUsing Virtual Folders<\/a>
\nDefining Conditional Settings<\/a><\/p>\n
<\/a>Overview<\/h2>\nUnlike the MSBuild-based<\/a> projects, Advanced CMake projects are completely independent from the regular Visual C++ Project Subsystem and are fully managed by VisualGDB. This enables a much deeper integration with the underlying build tools and also allows having multiple targets (e.g. executables or libraries) per project:![\"\"](\"https:\/\/visualgdb.com\/w\/wp-content\/uploads\/2020\/04\/nodes.png\")
<\/a><\/p>\n<\/a>Structure<\/h2>\nA typical Advanced CMake project consists of the following parts:<\/p>\n
\n- One or more CMakeLists.txt<\/strong> files (and *.cmake<\/strong> files included from them) that actually describe the project structure (targets, files, build settings, etc.).<\/li>\n
- The .vgdbcmake<\/strong> file that contains VisualGDB-level settings (e.g. how to transfer source files to the target, or how to debug the project).<\/li>\n<\/ul>\n
The project structure (targets, source files, etc) are not duplicated in the .vgdbsettings<\/strong> file. Instead, they are queried directly from CMake and rendered in Solution Explorer. Using Solution Explorer to add new files, or change any settings will directly update the necessary statements in CMakeLists.txt<\/strong>:![\"\"](\"https:\/\/visualgdb.com\/w\/wp-content\/uploads\/2020\/04\/lists.png\")
<\/a><\/p>\n<\/a>Settings<\/h2>\nThe Advanced CMake Projects have 4 types of settings shown below:<\/p>\n
<\/a><\/p>\n<\/a>Structure<\/h2>\nA typical Advanced CMake project consists of the following parts:<\/p>\n
\n- One or more CMakeLists.txt<\/strong> files (and *.cmake<\/strong> files included from them) that actually describe the project structure (targets, files, build settings, etc.).<\/li>\n
- The .vgdbcmake<\/strong> file that contains VisualGDB-level settings (e.g. how to transfer source files to the target, or how to debug the project).<\/li>\n<\/ul>\n
The project structure (targets, source files, etc) are not duplicated in the .vgdbsettings<\/strong> file. Instead, they are queried directly from CMake and rendered in Solution Explorer. Using Solution Explorer to add new files, or change any settings will directly update the necessary statements in CMakeLists.txt<\/strong>:<\/a><\/p>\n<\/a>Settings<\/h2>\nThe Advanced CMake Projects have 4 types of settings shown below:<\/p>\n
The project structure (targets, source files, etc) are not duplicated in the .vgdbsettings<\/strong> file. Instead, they are queried directly from CMake and rendered in Solution Explorer. Using Solution Explorer to add new files, or change any settings will directly update the necessary statements in CMakeLists.txt<\/strong>: The Advanced CMake Projects have 4 types of settings shown below:<\/p>\n<\/a><\/p>\n<\/a>Settings<\/h2>\n
![\"\"](\"https:\/\/visualgdb.com\/w\/wp-content\/uploads\/2020\/04\/new-1.png\")
<\/a>Selecting the same command in the target’s<\/strong> menu will add source files to the target instead.<\/p>\n![\"\"](\"https:\/\/visualgdb.com\/w\/wp-content\/uploads\/2020\/04\/ninja.png\")
<\/a>We recommend using Ninja instead of GNU Make, if your project and target supports its. Ninja works much faster on multi-core systems and is better integrated with the “project is out-of-date” check.<\/p>\n![\"\"](\"https:\/\/visualgdb.com\/w\/wp-content\/uploads\/2020\/04\/debug.png\")
<\/a><\/p>\n![\"\"](\"https:\/\/visualgdb.com\/w\/wp-content\/uploads\/2020\/04\/export.png\")
<\/a>First, reload the project via Solution Explorer. Then check the VisualGDB Build window. If it shows both configuration and build logs, make sure you select Configuration<\/strong>. Finally, locate the build command line ![\"\"](\"https:\/\/visualgdb.com\/w\/wp-content\/uploads\/2020\/04\/vars.png\")
<\/a><\/p>\n![\"\"](\"https:\/\/visualgdb.com\/w\/wp-content\/uploads\/2020\/04\/group.png\")
<\/a>There you can set the following options:<\/p>\n![\"\"](\"https:\/\/visualgdb.com\/w\/wp-content\/uploads\/2020\/04\/levels.png\")
<\/a><\/li>\n![\"\"](\"https:\/\/visualgdb.com\/w\/wp-content\/uploads\/2020\/04\/paths.png\")
<\/a><\/li>\n![\"\"](\"https:\/\/visualgdb.com\/w\/wp-content\/uploads\/2020\/04\/types.png\")
<\/a>Note that this setting does not affect built-in nodes like Embedded Resources<\/strong> or Linker Scripts<\/strong>.<\/li>\n![\"\"](\"https:\/\/visualgdb.com\/w\/wp-content\/uploads\/2020\/04\/targets.png\")
<\/a><\/li>\n![\"\"](\"https:\/\/visualgdb.com\/w\/wp-content\/uploads\/2020\/04\/newfolder-1.png\")
<\/a>After the folder is created, you can drag targets or sources into it, and VisualGDB will remember it next time you open the project. The mappings between the target\/source paths and virtual folders are stored in the .vgdbcmake<\/strong> files.<\/p>\n![\"\"](\"https:\/\/visualgdb.com\/w\/wp-content\/uploads\/2020\/04\/macro-1.png\")
<\/a>Note that each time you change these settings, VisualGDB will create or update a statement in one of the CMakeLists.txt<\/strong> files. You can make this statement conditional by wrapping it in ![\"\"](\"https:\/\/visualgdb.com\/w\/wp-content\/uploads\/2020\/04\/dbg.png\")
<\/a>E.g. the following code will add the MYMACRO definition to debug configuration only:<\/p>\n