{"id":27555,"date":"2021-02-09T16:00:05","date_gmt":"2021-02-09T16:00:05","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/cppblog\/?p=27555"},"modified":"2021-02-09T15:58:48","modified_gmt":"2021-02-09T15:58:48","slug":"visual-studio-code-c-extension-cross-compilation-intellisense-configurations","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/cppblog\/visual-studio-code-c-extension-cross-compilation-intellisense-configurations\/","title":{"rendered":"Visual Studio Code C++ Extension: Cross-Compilation IntelliSense Configurations"},"content":{"rendered":"

The February 2021 update of the Visual Studio Code C++ extension<\/a> is now available! This latest release provides support for cross-compilation IntelliSense configurations<\/a> and over 60 bug fixes! To find out more about all the enhancements, check out our\u00a0release notes on GitHub.<\/a><\/p>\n

Cross-compilation IntelliSense configurations<\/h3>\n

With this latest release, you can configure the extension to provide proper IntelliSense when compiling for a different platform<\/em> than your host OS. That\u2019s right\u2014 platform<\/em>, not just architecture. The C++ extension no longer hardcodes system defines based on your host OS; it\u2019ll use the system defines returned by your compiler.<\/p>\n

Let\u2019s say you\u2019re developing on macOS and your project targets Linux. Assuming you have a compiler compatible with your project\u2019s target platform and architecture, the C++ extension will query that compiler using the Compiler path<\/strong>, Compiler arguments, <\/strong>and IntelliSense mode<\/strong> settings in your IntelliSense configuration. If you\u2019re using a custom configuration provider (like CMake Tools) or compile_commands.json, then you don\u2019t need to worry about updating the C++ extension\u2019s IntelliSense configuration; everything should just work.<\/p>\n

Your project\u2019s IntelliSense configurations are stored in the c_cpp_properties.json file under the .vscode folder. Edit these settings by selecting C\/C++: Edit Configurations (UI)<\/strong> from the Command Palette.<\/p>\n

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

Under your configuration\u2019s Compiler path <\/strong>setting, <\/strong>enter the path to the compiler compatible with your target platform and architecture.<\/p>\n

Then use Compiler arguments<\/strong> to provide the target triplet that you use when cross-compiling your code with your compiler. For example, –target=x86_64-linux<\/em> if you\u2019re targeting Linux 64-bit. This allows the C++ extension to query the compiler for system defines and include paths specific to your target platform and architecture.<\/p>\n

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

Next, set IntelliSense mode<\/strong> to the platform- and architecture-specific variant of the compiler you\u2019re using (it should closely match the target triplet defined in Compiler arguments<\/strong>). If the information returned from querying the compiler doesn\u2019t match the IntelliSense mode <\/strong>you chose, the C++ extension will automatically correct the IntelliSense mode for you.<\/p>\n

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

Now when you open your project in VS Code, you\u2019ll get IntelliSense for your target platform instead of macOS. No more squiggles from hardcoded system defines!<\/p>\n

Additional enhancements<\/h3>\n

In addition to supporting cross-compilation IntelliSense configurations, the February 2021 update comes with the following enhancements:<\/p>\n