{"id":25532,"date":"2020-02-07T23:07:37","date_gmt":"2020-02-07T23:07:37","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/cppblog\/?p=25532"},"modified":"2020-02-07T23:08:31","modified_gmt":"2020-02-07T23:08:31","slug":"visual-studio-code-cmake-tools-extension-multi-root-workspaces-and-file-based-api","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/cppblog\/visual-studio-code-cmake-tools-extension-multi-root-workspaces-and-file-based-api\/","title":{"rendered":"Visual Studio Code CMake Tools Extension: Multi-root workspaces and file-based API"},"content":{"rendered":"

The February 2020 update of the Visual Studio Code CMake Tools extension<\/a> is now available. This release includes two of the extension\u2019s top feature requests: file-based API support<\/a> and multi-root workspaces<\/a>. For a full list of this release\u2019s improvements check out the release notes on GitHub<\/a>.<\/p>\n

Multi-root workspace support<\/h4>\n

The latest release of the CMake Tools extension comes with support for multi-root workspaces. This means you can have two or more folders containing a root CMakeLists.txt open side-by-side in Visual Studio Code. When a workspace contains multiple folders, the CMake Tools extension will display the active folder <\/strong>in the left-hand side of the status bar. The active folder is the folder to which all CMake-specific commands (configure, build, debug, etc.) are applied. In the following example my active folder is CMakeProject-1.<\/p>\n

\"Status<\/p>\n

By default, the active folder will change based on your file context. Viewing or editing a file in CMakeProject-1 will cause CMakeProject-1 to be the active folder, while viewing or editing a file in CMakeProject-2 will cause CMakeProject-2 to be the active folder. You can temporarily override the active folder by selecting the active folder in the status bar or running the CMake: Select Active Folder <\/strong>command.<\/p>\n

\"The<\/p>\n

You can also disable this behavior by setting the user-level or workspace-level setting<\/a> CMake:<\/strong> Auto Select Active Folder<\/strong> to false. To open your workspace settings, use the command \u201cWorkspaces: Open Workspace Configuration File\u201d. If cmake.autoSelectActiveFolder is set to false then your active folder will only change if you manually run the CMake: Select Active Folder<\/strong> command.<\/p>\n

Finally, the CMake Tools extension has also added new commands like CMake: Configure All Projects <\/strong>and CMake: Build All Projects <\/strong>to apply existing CMake commands to all the folders in your workspace. These commands are only available when you have more than one folder open in your workspace.<\/p>\n

\"'All'<\/p>\n

Commands to configure, build, clean, rebuild and reconfigure all projects are also available from the CMake: Project Outline<\/strong> view.<\/p>\n

File-based API<\/h4>\n

Thank you to @KoeMai<\/a> for submitting this PR!<\/p>\n

CMake version 3.14 introduced file-based API<\/a>, which is a new way for clients (like the CMake Tools extension) to get semantic information about the underlying build system generated by CMake. It allows the client to write query files prior to build system generation. During build system generation CMake will read those query files and write object model response files for the client to read. Previously the CMake Tools extension only supported cmake-server<\/a> mode, which was deprecated with CMake version 3.15. File-based API provides a faster and more streamlined way for the extension to populate the editor with information specific to your project structure because it is reading response files instead of running CMake in long-running server mode.<\/p>\n

The latest release of the CMake Tools extension supports file-based API. The setting CMake: CMake Communication Mode <\/strong>has been added with the following possible values. The default value is automatic<\/strong>.<\/p>\n