{"id":24371,"date":"2019-05-28T13:16:20","date_gmt":"2019-05-28T13:16:20","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/cppblog\/?p=24371"},"modified":"2019-05-28T17:30:17","modified_gmt":"2019-05-28T17:30:17","slug":"cmake-3-14-and-performance-improvements","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/cppblog\/cmake-3-14-and-performance-improvements\/","title":{"rendered":"CMake 3.14 and Performance Improvements"},"content":{"rendered":"

In Visual Studio 2019 version 16.1<\/a> we have updated the version of CMake we ship inbox to CMake 3.14. This comes with performance improvements for extracting generated build system information. Additionally, we now support virtually all the Visual Studio capabilities regardless of the CMake binary origin so long as the CMake version is at least 3.14. The main reason for this is the introduction of the file-based API<\/a>, which we now support, and which provides a new way for retrieving semantic information. This is now the recommended way to connect an IDE to CMake, the old CMake server being deprecated, and we are an early adopter of the feature.<\/p>\n

Visual Studio Performance Improvements<\/h2>\n

\"Graph<\/p>\n

The indexing is now significantly faster for code opened via Open folder, and as a result IntelliSense is available considerably faster than in Visual Studio 2017. As an example, in the LLVM codebase<\/a>, IntelliSense becomes available at least 2 times faster in Visual Studio 2019. Additionally, a new indexing algorithm lights up IntelliSense incrementally while the folder is being indexed.<\/p>\n

In Visual Studio 2017 on average it takes 3 min from the point of opening the LLVM folder, to the point where you have IntelliSense, including generation. In Visual Studio 2019 it takes 1:26 min, including generation.<\/p>\n

CMake 3.14<\/h2>\n

We now ship CMake 3.14 in-box with Visual Studio. This contains the new file-based API, and support for the Visual Studio 2019 generators. To see the full set of changes, please see the CMake 3.14 release notes<\/a>.<\/p>\n

Visual Studio 2019 Generators<\/h2>\n

\"CMake<\/p>\n

CMake 3.14 introduces support for the Visual Studio 2019 generators<\/a>. The new generator is called \u201cVisual Studio 16 2019\u201d, and the platform targeting is simplified. To use a specific platform, use the -A argument. For example, to use the Visual Studio 2019 generator targeting the x64 platform: cmake.exe -G \u201cVisual Studio 16 2019\u201d -A x64<\/p>\n

File-based API<\/h2>\n

The file-based API<\/a> allows a 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. Prior to this API’s introduction we were using the cmake-server<\/a> to get the equivalent information. We\u2018re still supporting the old model, but starting with 3.14 we can now support the new model as well. One of the differences in our CMake fork on github<\/a> was the backtrace information needed for our Targets View feature inside Visual Studio. Prior to CMake 3.14 we needed the CMake version from our fork, in order for Targets View to work properly. Now, with the file-based API this is no longer required.<\/p>\n

The file-based API provides a simpler, standard path to the future, with official support in CMake itself. We expect most users to see either performance improvements or not notice any degradation of performance. Extracting the information to populate the Visual Studio UI is faster because we are just reading the response files rather than running CMake in long-running server mode, there is less memory usage and less overhead associated with creating and maintaining processes.<\/p>\n

These value-added features light up automatically when you update to Visual Studio 2019 version 16.1 Preview 2.<\/p>\n

Send Us Feedback<\/h2>\n

Your feedback is a critical part of ensuring that we can deliver the best CMake experience.\u202f We would love to know how Visual Studio 2019 version 16.1<\/a>\u202fis working for you.\u202fIf you have any questions specific to CMake Tools, please reach out to\u202fcmake@microsoft.com or leave a comment.\u202fIf you find any issues or have a suggestion, the best way to reach out to us is to\u202fReport a Problem<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

In Visual Studio 2019 version 16.1 we have updated the version of CMake we ship inbox to CMake 3.14. This comes with performance improvements for extracting generated build system information. Additionally, we now support virtually all the Visual Studio capabilities regardless of the CMake binary origin so long as the CMake version is at least […]<\/p>\n","protected":false},"author":4522,"featured_media":24407,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[270],"tags":[],"class_list":["post-24371","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-announcement"],"acf":[],"blog_post_summary":"

In Visual Studio 2019 version 16.1 we have updated the version of CMake we ship inbox to CMake 3.14. This comes with performance improvements for extracting generated build system information. Additionally, we now support virtually all the Visual Studio capabilities regardless of the CMake binary origin so long as the CMake version is at least […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts\/24371","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\/4522"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/comments?post=24371"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts\/24371\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/media\/24407"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/media?parent=24371"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/categories?post=24371"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/tags?post=24371"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}