To view the full list of updates with this release, please look at our CHANGELOG<\/a>. This release features 2 contributions from our open-source community, and we greatly thank you for your support!<\/p>\n Kitware has added two new CMake Presets in version 6: workflow and package presets. Workflow presets allow you to define a string of CMake presets that you want to execute (e.g.\u00a0 a configure action followed by a build action). Package presets are presets that invoke CPack to package your software based on a variety of specifications. You can learn more about these presets from Kitware\u2019s CMake Presets documentation.<\/a> There is now added support to include these new preset types in your CMake presets file and invoke them through the extension.<\/p>\n With this added capability, you can select and run these presets by default from the CMake Side bar as you would any other preset.<\/p>\n Additionally, you can toggle the presets visibility across the side bar and status bar via the CMake Status Bar Visibility options through \u201c While CMake Presets v7 and v8 do not have official support yet in the product, expansion of One of our most highly-upvoted tickets was to add adjustments to CMake Presets by overriding\/adding to cache variables. There are now new settings.json <\/strong>fields that modify configuration, build, and testing to override CMake Presets environments and arguments if you require this workflow. Specifically, these fields include:<\/p>\n Overrides any CMake command:<\/em><\/p>\n Overrides configure CMake commands<\/em><\/p>\n Overrides build CMake commands<\/em><\/p>\n Overrides test CMake commands<\/em><\/p>\n If there are settings set in any of the above fields, the affected CMake presets will display in the UI whether override settings have been applied for ease of tracking.<\/p>\n Additionally, a setting icon will appear that, when clicked, will open to the possible settings that may be affecting the configuration.<\/p>\n If you commonly perform any type of CMake command, you can now pin these commands to the CMake side bar so that they\u2019re easily accessible. To add a new CMake command to the side bar, navigate to the Pinned CMake Commands<\/strong> section and select the plus sign to search for a new CMake command to add.<\/p>\n To run any given command, just hover over the command and select the corresponding play button. You can also remove any command from the list by hovering over it, right-clicking, and selecting Unpin Command<\/strong>.<\/p>\n We have a lot of exciting new things planned for the 1.18 release including adding the first layers of CMake language services to the extension<\/a>, adding tasks to the CMake side bar<\/a>, and having an option for CMake to be automatically installed when missing via package manager<\/a>. You can view these plans any time via our new GitHub project view<\/a>.<\/p>\n Let our team know what else you would like to see from us by\u00a0adding an issue to our repo<\/a>\u00a0or upvoting any existing issues with a thumbs up.<\/p>\n Download the\u00a0CMake\u00a0Tools extension\u00a0<\/a>for Visual Studio Code and let us know what you think.\u00a0We would love to see what you contribute to our\u00a0repo<\/a>\u00a0and we are active on reviews and collaboration. Comment below or reach us via email at\u00a0visualcpp@microsoft.com<\/a>\u00a0or via\u00a0Twitter at\u00a0@VisualC<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":" The February release of the CMake Tools extension in VS Code is now available. With this release, we have three major new updates to the extension, including some of our highly upvoted requests: There is now support for CMake Presets v6, which includes the new workflow presets and package presets. (Issue #2871) You can now […]<\/p>\n","protected":false},"author":85413,"featured_media":33671,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[266,275],"tags":[],"class_list":["post-33670","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cmake","category-visual-studio-code"],"acf":[],"blog_post_summary":" The February release of the CMake Tools extension in VS Code is now available. With this release, we have three major new updates to the extension, including some of our highly upvoted requests: There is now support for CMake Presets v6, which includes the new workflow presets and package presets. (Issue #2871) You can now […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts\/33670","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/users\/85413"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/comments?post=33670"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts\/33670\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/media\/33671"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/media?parent=33670"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/categories?post=33670"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/tags?post=33670"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}CMake Presets v6 Support<\/h3>\n
![\"The](\"https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2024\/02\/cmake-sidebar-package-workflow.png\")
<\/a><\/p>\nworkflow<\/code>\u201d<\/strong>, \u201cworkflowPreset<\/code>\u201d<\/strong>, and \u201cpackagePreset<\/code>\u201d<\/strong> settings. To learn more about the supported visibility options, please see our documentation<\/a>.<\/p>\n$penv{}<\/code> in #include was added in the previous 1.16 release<\/a> of the extension. We will be working to add the full support for v7 and v8 in upcoming releases.<\/p>\nOverride\/add to cache variables when using CMake Presets<\/h3>\n
\n
cmake.environment<\/code><\/li>\n<\/ul>\n\n
cmake.configureArgs<\/code><\/li>\n<\/ul>\n\n
cmake.buildArgs<\/code><\/li>\ncmake.buildEnvironment<\/code><\/li>\ncmake.buildToolsArgs<\/code><\/li>\n<\/ul>\n\n
cmake.ctestArgs<\/code><\/li>\ncmake.testEnvironment<\/code><\/li>\n<\/ul>\n![\"An](\"https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2024\/02\/configure-args-override-1024x560.png\")
<\/a><\/p>\n![\"A](\"https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2024\/02\/settings-override-icon-1024x618.png\"){kind=icon}
<\/a><\/p>\nPin common CMake commands to side bar<\/h3>\n
![\"An](\"https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2024\/02\/cmake-pinned-commands.png\")
<\/a><\/p>\n![\"Whenever](\"https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2024\/02\/cmake-unpin-commands-1024x299.png\")
<\/a>What’s next?<\/h3>\nWhat do you think?<\/h3>\n