{"id":33113,"date":"2023-11-15T16:54:29","date_gmt":"2023-11-15T16:54:29","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/cppblog\/?p=33113"},"modified":"2023-11-16T18:55:07","modified_gmt":"2023-11-16T18:55:07","slug":"visual-studio-code-cmake-tools-extension-1-16-update-new-cmake-tools-sidebar-and-cmake-debugging-options","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/cppblog\/visual-studio-code-cmake-tools-extension-1-16-update-new-cmake-tools-sidebar-and-cmake-debugging-options\/","title":{"rendered":"Visual Studio Code CMake Tools Extension 1.16 Update: New CMake Tools Sidebar and CMake Debugging options"},"content":{"rendered":"

The <\/span>November release of the CMake Tools extension<\/span><\/a> in VS Code is now available. With this release, we have two major new updates to the extension:<\/span>\u00a0<\/span><\/p>\n

    \n
  1. A new, customizable CMake Tools status bar and side bar for your presets and CMake actions<\/span>\u00a0<\/span><\/li>\n
  2. Script mode debugging support for the CMake Debugger<\/span>\u00a0<\/span><\/li>\n<\/ol>\n

    The full list of updates can be seen in our <\/span>change log<\/span><\/a>. This release features 10 contributions from the open-source community. Thank you all for your continued support!<\/span>\u00a0<\/span><\/p>\n

    Release Schedule Updates<\/em><\/h4>\n

    Starting with this <\/span>November <\/span>release, <\/span>CMake<\/span> Tools will <\/span>now <\/span>release<\/span> every 3 months. You can learn more about our release schedules on <\/span>our<\/span> <\/span>r<\/span>elease schedule wiki<\/span><\/span><\/a>.<\/span><\/span>\u00a0<\/span><\/p>\n

    Updates to the default CMake Tools UI<\/h3>\n

    Starting <\/span>in<\/span> this <\/span>1.16<\/span> re<\/span>l<\/span>ease<\/span>, the default <\/span>CMake<\/span> Tools status bar will only have <\/span>commonly-used<\/span> actions like <\/span><\/span>Build<\/span><\/span><\/strong>, <\/span><\/span>Debug<\/span><\/span><\/strong>, and <\/span><\/span>Run<\/span><\/span><\/strong> to de-clutter the status bar by default. All options for configuring your project through <\/span>CMake<\/span> presets or kits\/variants will be found in the <\/span>CMake<\/span> Tools side bar under their respective node.<\/span> There are <\/span>new items<\/span> for <\/span>Deleting Cache and Reconfiguring<\/span> and accessing <\/span>CMake<\/span> settings<\/span> at the top of the Project Status view<\/span>.<\/span><\/span>\u00a0<\/span><\/p>\n

    New CMake Tools Sidebar<\/em><\/h5>\n

    \"The<\/a><\/p>\n

    Under each <\/span>respective <\/span>node, you will be able to <\/span>view and toggle<\/span> your active <\/span>CMake<\/span> presets and targets<\/span>\u00a0<\/span>and perform Configure, Build, Test, Debug, and Launch actions on <\/span>your project<\/span> configurations. This will <\/span>provide<\/span> a one-stop location to view and edit all your <\/span>CMake<\/span> configurations by default.<\/span><\/span>\u00a0<\/span><\/p>\n

    New Simplified CMake Status Bar Items<\/em><\/h5>\n

    \"The<\/a><\/p>\n

    The previous status bar displayed a plethora of CMake configuration options, but with the new default, you will have access to only the commonly-used CMake actions in the status bar in order to clean up space in the view by default. Then, you can expand the CMake sidebar for your configuration needs.<\/p>\n

    This view can be customized to suit your needs, so you can pull whatever relevant items you want to the status bar and configure the amount of space each command takes up.<\/p>\n

    If you have any other feedback on this new experience, please comment on our open GitHub issue<\/a>.<\/p>\n

    Added script mode for the CMake Debugger<\/h3>\n

    We have now added support for users to use the CMake debugger to debug externally launched CMake processes or any generic CMake script. To do so, please add cmakeDebugType<\/code> to your launch.json<\/code> \u00a0configurations to specify whether you are debugging with the three available modes: configure<\/code>, external<\/code>, and script<\/code>.<\/p>\n

    Example launch.json with CMake debug types<\/em><\/h5>\n
    {\r\n       \u201cconfigurations\u201d: [\r\n           {\r\n                \u201ctype\u201d: \u201ccmake\u201d,\r\n                \u201crequest\u201d: \u201claunch\u201d,\r\n                \u201cname\u201d: \u201cDebug CMake script\u201d,\r\n                \u201ccmakeDebugType\u201d: \u201cscript\u201d,\r\n                \u201cscriptPath\u201d \u201c${workspaceFolder}\/anyScript.cmake\r\n          },\r\n          {\r\n                \u201ctype\u201d: \u201ccmake\u201d,\r\n                \u201crequest\u201d: \u201claunch\u201d,\r\n                \u201cname\u201d: \u201cDebug externally launched CMake processes\u201d,\r\n                \u201ccmakeDebugType\u201d: \u201cexternal\u201d\r\n                \u201cpipeName\u201d: \u201c<insert-pipe-name>\u201d\r\n          }\r\n      ]\r\n}<\/pre>\n
    To learn more about the supported CMake debug variables in your launch.json, please see our CMake debug documentation<\/a>.<\/p>\n
    You can also debug vcpkg portfiles using the CMake Debugger in the new script mode. source cross-platform library manager that uses portfiles to know how to acquire, build, and install libraries. Debugging portfiles can be helpful whenever you are adding a new library of your own to the vcpkg catalog. To learn more, please see our blog post on debugging vcpkg portfiles<\/a>.<\/p>\n
    What’s next?<\/h3>\n
    For our next release of CMake Tools, we are planning to incorporate CMake Tasks into the CMake side bar and overall integrate better with the Cpp Tools extension for actions like . If you would like to add any feedback for this, please comment on our open issue<\/a> for the side bar and our open issue for integrating with Run\/Debug<\/a>.<\/p>\n
    Additionally, we will be working to add CMakePresets v6 support<\/a> to the extension, so that you can use Kitware\u2019s new Workflow and Package presets.<\/p>\n
    Let our team know what else you would like to see from us by adding an issue to our repo<\/a> or upvoting any existing issues with a thumbs up.<\/p>\n
    What do you think?<\/h3>\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 November release of the CMake Tools extension in VS Code is now available. With this release, we have two major new updates to the extension:\u00a0 A new, customizable CMake Tools status bar and side bar for your presets and CMake actions\u00a0 Script mode debugging support for the CMake Debugger\u00a0 The full list of updates […]<\/p>\n","protected":false},"author":85413,"featured_media":35994,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1,266,275],"tags":[],"class_list":["post-33113","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cplusplus","category-cmake","category-visual-studio-code"],"acf":[],"blog_post_summary":"
    The November release of the CMake Tools extension in VS Code is now available. With this release, we have two major new updates to the extension:\u00a0 A new, customizable CMake Tools status bar and side bar for your presets and CMake actions\u00a0 Script mode debugging support for the CMake Debugger\u00a0 The full list of updates […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts\/33113","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=33113"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts\/33113\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/media\/35994"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/media?parent=33113"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/categories?post=33113"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/tags?post=33113"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}