{"id":24889,"date":"2019-08-16T15:45:30","date_gmt":"2019-08-16T15:45:30","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/cppblog\/?p=24889"},"modified":"2019-08-16T15:45:30","modified_gmt":"2019-08-16T15:45:30","slug":"c-cross-platform-development-with-visual-studio-2019-version-16-3-vcpkg-cmake-configuration-remote-headers-and-wsl","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/cppblog\/c-cross-platform-development-with-visual-studio-2019-version-16-3-vcpkg-cmake-configuration-remote-headers-and-wsl\/","title":{"rendered":"C++ Cross-Platform Development with Visual Studio 2019 version 16.3: vcpkg, CMake configuration, remote headers, and WSL"},"content":{"rendered":"

In Visual Studio 2019 you can target both Windows and Linux from the comfort of a single IDE<\/span><\/span>.\u00a0<\/span><\/span>Visual Studio\u2019s native support for CMake<\/span><\/span><\/a>\u00a0<\/span><\/span>lets<\/span><\/span>\u00a0you<\/span><\/span>\u00a0open any folder containing C++ code and a CMakeLists.txt file\u00a0<\/span><\/span>directly in Visual Studio\u00a0<\/span><\/span>to<\/span><\/span>\u00a0edit, build, and debug your\u00a0<\/span><\/span>CMake<\/span><\/span>\u00a0project on<\/span><\/span>\u00a0Windows<\/span><\/span>,<\/span><\/span>\u00a0Linux<\/span><\/span>, and\u00a0<\/span><\/span>the\u00a0<\/span><\/span>Windows Subsystem for Linux (WSL)<\/span><\/span><\/a>.<\/span><\/span>\u00a0<\/span><\/span>Visual Studio\u2019s\u00a0<\/span><\/span>MSBuild-based Linux support<\/span><\/span><\/a>\u00a0allows you\u00a0<\/span><\/span>to create a<\/span><\/span>nd debug <\/span><\/span>console applications<\/span><\/span> that execute on a remote Linux system or\u00a0<\/span><\/span>WSL<\/span><\/span>.<\/span><\/span>\u00a0<\/span><\/span>For\u00a0<\/span><\/span>either<\/span><\/span>\u00a0of these scenarios<\/span><\/span>,<\/span><\/span>\u00a0the\u00a0<\/span><\/span>Linux development with C++ workload<\/span><\/span><\/a>\u00a0is required.\u00a0<\/span><\/span>\u00a0<\/span><\/p>\n

Visual Studio 2019 version 16.3\u00a0<\/span><\/span>Preview\u00a0<\/span><\/span>2\u00a0<\/span><\/span>introduces\u00a0<\/span><\/span>several improvements specific\u00a0<\/span><\/span>to\u00a0<\/span><\/span>Visual Studio\u2019s native\u00a0<\/span>CMake<\/span>\u00a0support and\u00a0<\/span>MSBuild<\/span>-based Linux support.\u00a0<\/span><\/span>If you are just getting started with Linux development in Visual Studio, I recommend trying\u00a0<\/span>our<\/span>\u00a0<\/span><\/span>native support for WSL<\/span><\/span><\/a>.\u00a0<\/span><\/span>\u00a0<\/span><\/p>\n

Install missing\u00a0<\/span><\/span>vcpkg<\/span>\u00a0packages with a quick action in\u00a0<\/span>CMake<\/span>\u00a0projects\u00a0<\/span><\/span>\u00a0<\/span><\/h3>\n

Vcpkg<\/span><\/span><\/a>\u00a0<\/span><\/span>helps you manage\u00a0<\/span><\/span>C and C++ libraries on Windows, Linux, and\u00a0<\/span><\/span>m<\/span><\/span>acOS<\/span><\/span>.\u00a0<\/span><\/span>In Visual Studio\u00a0<\/span><\/span>2019 version 16.3 we have\u00a0<\/span><\/span>improv<\/span><\/span>ed\u00a0<\/span><\/span>vcpkg<\/span><\/span>\u00a0integration in Visual Studio for\u00a0<\/span><\/span>CMake<\/span><\/span>\u00a0projects<\/span><\/span>\u00a0that are using the\u00a0<\/span><\/span>vcpkg toolchain file<\/span><\/span><\/a>\u00a0and have run\u00a0<\/span><\/span>\u2018<\/span><\/span>vcpkg integrate install<\/span><\/span><\/a>\u2019<\/span><\/span>.<\/span><\/span>\u00a0<\/span><\/span>You will now be prompted to install\u00a0<\/span><\/span>missing\u00a0<\/span><\/span>vcpkg<\/span><\/span>\u00a0packages\u00a0<\/span><\/span>via a\u00a0<\/span><\/span>quick action<\/span><\/span>:<\/span><\/span><\/p>\n

\"Add<\/p>\n

Selecting \u201cInstall package\u2026\u201d will automatically\u00a0<\/span><\/span>install the missing package (and all required dependencies)\u00a0<\/span><\/span>using\u00a0<\/span><\/span>v<\/span><\/span>cpkg<\/span>\u00a0<\/span><\/span>and\u00a0<\/span><\/span>route all output to the\u00a0<\/span><\/span>Output Window.\u00a0<\/span><\/span>\u00a0<\/span><\/span>\u00a0<\/span><\/p>\n

CMake<\/span>\u00a0Settings Editor usability improvements\u00a0<\/span><\/span>\u00a0<\/span><\/h3>\n

We\u2019ve\u00a0<\/span><\/span>made it easier to configure\u00a0<\/span>CMake<\/span>\u00a0projects in Visual Studio by\u00a0<\/span><\/span>improving\u00a0<\/span><\/span>property descriptions in the\u00a0<\/span><\/span>CMake Settings Editor<\/span><\/span><\/a>\u00a0and providing\u00a0<\/span><\/span>in-editor\u00a0<\/span><\/span>links to relevant documentation.\u00a0<\/span><\/span>\u00a0<\/span><\/p>\n

\"The<\/p>\n

The CMake Settings Editor now maps Visual Studio properties to the corresponding CMake variable (e.g. configuration type to CMAKE_BUILD_TYPE) and describes other tools (vcpkg, rsync) that can be configured in Visual Studio.\u00a0\u00a0<\/span><\/span>\u00a0<\/span><\/p>\n

Remote header performance improvements for Linux projects<\/span><\/span>\u00a0<\/span><\/h3>\n

When you\u00a0<\/span><\/span>connect to a remote Linux system<\/span><\/span><\/a>, Visual Studio automatically\u00a0<\/span><\/span>copies<\/span><\/span>\u00a0the include directories for the compiler\u00a0<\/span><\/span>from<\/span><\/span>\u00a0the\u00a0<\/span><\/span>remote system<\/span><\/span>\u00a0to Windows to provide IntelliSense as if you were working<\/span><\/span>\u00a0<\/span><\/span>on your remote machine.\u00a0<\/span><\/span>In\u00a0<\/span><\/span>Visual Studio\u00a0<\/span><\/span>2019\u00a0<\/span><\/span>version<\/span><\/span>\u00a016.3 Preview 2\u00a0<\/span><\/span>the remote header copy<\/span><\/span>\u00a0has been optimized\u00a0<\/span><\/span>and\u00a0<\/span><\/span>now\u00a0<\/span><\/span>runs in parallel. This leads to<\/span><\/span>\u00a0performance improvements for large codebases<\/span><\/span>.<\/span><\/span>\u00a0<\/span><\/span>For example,<\/span><\/span>\u00a0the\u00a0<\/span><\/span>initial\u00a0<\/span><\/span>remote header sync for<\/span><\/span>\u00a0<\/span><\/span>MySQL Server<\/span><\/span><\/a>\u00a0now runs\u00a0<\/span><\/span>~<\/span><\/span>3<\/span><\/span>0<\/span><\/span>% faster<\/span><\/span>.<\/span><\/span>\u00a0<\/span><\/span>Performance improvements for your own codebase may vary.<\/span><\/span><\/p>\n

These performance improvements apply to both\u00a0<\/span><\/span>CMake<\/span><\/span>\u00a0Linux projects and\u00a0<\/span><\/span>MSBuild<\/span><\/span>-based Linux projects.\u00a0<\/span><\/span>More<\/span><\/span>\u00a0IntelliSense improvements for Linux projects are coming soon<\/span><\/span>\u00a0and will be available in a future release<\/span><\/span>, so stay tuned.\u00a0<\/span><\/span>\u00a0<\/span><\/p>\n

Improvements to Visual Studio\u2019s native support for WSL\u00a0<\/span><\/span>\u00a0<\/span><\/h3>\n

In Visual Studio 2019 version 16.1 we announced\u00a0<\/span><\/span>native support for C++ with WSL<\/span><\/span><\/a>. This allows you to build and debug on your local WSL installation without adding a remote connection or configuring SSH.\u00a0 In Visual Studio 2019 version 16.3 Preview\u00a0<\/span><\/span>2\u00a0<\/span><\/span>we have added support for parallel builds for\u00a0<\/span><\/span>MSBuild<\/span><\/span>-based Linux projects targeting WSL<\/span><\/span>. You can configure the maximum number of compilation processes to be created in parallel via\u00a0<\/span><\/span>Properties\u00a0<\/span><\/span>> C\/C++ > General > Max Parallel Compilation Jobs:\u00a0<\/span><\/span>\u00a0<\/span><\/p>\n

\"Configure<\/p>\n

Support for parallel compilation jobs<\/span><\/span>\u00a0has been added for WSL applications that use\u00a0<\/span><\/span>gcc<\/span>\u00a0or\u00a0<\/span><\/span>Clang.<\/span><\/span><\/a>\u00a0<\/span><\/p>\n

We also added support for WSL build events for\u00a0<\/span><\/span>MSBuild<\/span><\/span>-based Linux projects targeting WSL. These events allow you to specify a command for the pre-build, pre-link, and post-build event tools to run in the WSL shell and can be configured via\u00a0<\/span><\/span>Properties<\/span><\/span>\u00a0> Build Events.\u00a0\u00a0<\/span><\/span>\u00a0<\/span><\/p>\n

\"Configure<\/p>\n

Resolved issues<\/h3>\n

The best way to report a problem or suggest a feature to the C++ team is via\u00a0<\/span><\/span>Developer Community<\/span><\/span><\/a>.<\/span><\/span>\u00a0The following feedback tickets related to C++ cross-platform de<\/span><\/span>velopment<\/span><\/span> are<\/span><\/span> resolved in Visual Studio 2019 version 16.3 (some fixes will be available soon in 16.3 Preview 3): <\/span><\/span>\u00a0<\/span><\/p>\n

VS2019 wipes\u00a0<\/span>CMake<\/span>\u00a0build\u00a0<\/span>directory<\/span>\u00a0each time I touch CMakeLists.txt<\/span><\/a>\u00a0<\/span><\/p>\n

CTest\u2019s<\/span>\u00a0<\/span>add_test<\/span>\u00a0passes\u00a0<\/span>incorrect<\/span>\u00a0number of arguments to command<\/span><\/a>\u00a0<\/span>\u00a0<\/span><\/p>\n

CMake<\/span>\u00a0cache generation always deletes\u00a0<\/span>build<\/span>\u00a0<\/span>directory<\/span>\u00a0if\u00a0<\/span>toolchain<\/span>\u00a0path has backslashes<\/span><\/a>\u00a0<\/span>\u00a0<\/span><\/p>\n

CMake<\/span>\u00a0Targets View \u2013 Targets have no\u00a0<\/span>CMakeLists<\/span>.txt if\u00a0<\/span>add_executable<\/span>(\/library) is called from a function defined in an included file<\/span><\/a>\u00a0<\/span><\/p>\n

CMake<\/span>\u00a0MSVC_TOOLSET_VERSION is incorrect in Visual Studio 2019<\/span><\/a>\u00a0<\/span><\/p>\n

VS API issue on\u00a0<\/span>CMake<\/span>\u00a0solutions in VS 16.2 Preview<\/span><\/a>\u00a0<\/span>\u00a0<\/span><\/p>\n

Talk to us!<\/h3>\n

Do you have feedback\u00a0<\/span><\/span>on our Linux tooling or\u00a0<\/span>CMake<\/span>\u00a0support in Visual Studio? We\u2019d love to hear your feedback\u00a0<\/span><\/span>to\u00a0<\/span><\/span>help us prioritize and\u00a0<\/span><\/span>build the right features for you. We can be reached via the comments below, email (<\/span><\/span>visualcpp@microsoft.com<\/span><\/span><\/a>), and Twitter\u00a0<\/span><\/span>(@VisualC<\/span><\/span><\/a>)<\/span><\/span>.<\/span><\/span>\u00a0<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

In Visual Studio 2019 you can target both Windows and Linux from the comfort of a single IDE.\u00a0Visual Studio\u2019s native support for CMake\u00a0lets\u00a0you\u00a0open any folder containing C++ code and a CMakeLists.txt file\u00a0directly in Visual Studio\u00a0to\u00a0edit, build, and debug your\u00a0CMake\u00a0project on\u00a0Windows,\u00a0Linux, and\u00a0the\u00a0Windows Subsystem for Linux (WSL).\u00a0Visual Studio\u2019s\u00a0MSBuild-based Linux support\u00a0allows you\u00a0to create and debug console applications that […]<\/p>\n","protected":false},"author":2953,"featured_media":24890,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[270,266,279,230,272],"tags":[],"class_list":["post-24889","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-announcement","category-cmake","category-linux","category-new-feature","category-vcpkg"],"acf":[],"blog_post_summary":"

In Visual Studio 2019 you can target both Windows and Linux from the comfort of a single IDE.\u00a0Visual Studio\u2019s native support for CMake\u00a0lets\u00a0you\u00a0open any folder containing C++ code and a CMakeLists.txt file\u00a0directly in Visual Studio\u00a0to\u00a0edit, build, and debug your\u00a0CMake\u00a0project on\u00a0Windows,\u00a0Linux, and\u00a0the\u00a0Windows Subsystem for Linux (WSL).\u00a0Visual Studio\u2019s\u00a0MSBuild-based Linux support\u00a0allows you\u00a0to create and debug console applications that […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts\/24889","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\/2953"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/comments?post=24889"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts\/24889\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/media\/24890"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/media?parent=24889"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/categories?post=24889"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/tags?post=24889"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}