User Guide

  • 2022.2
  • 04/11/2022
  • Public Content

Developing a Visual Studio Code* Project for SSH Development on Windows Subsystem for Linux*

Using Visual Studio Code* with Intel® oneAPI Toolkits
This guide assumes you are familiar with C/C++ development and the Visual Studio Code (VS Code) editor. If you are new to Visual Studio Code, review these VS Code documentation links:
The following procedure will use a Remote Host connection enabling you to edit and debug your code using the Windows Subsystem for Linux* (WSL).


It is not necessary to install VS Code on your Linux target that is running on WSL. VS Code is only needed on your Windows development system. The Linux installed on WSL does not require a GUI in order to be used for Linux development.

Set oneAPI Environment Variables on the WSL Target Linux

In order to perform development on your remote WSL target, you must install (at minimum) the Intel® oneAPI Base Toolkit (Base Kit) and configure the oneAPI development environment variables on the WSL target Linux. The recommended installation method is Installing via Linux* Package Managers.
  1. Open a WSL terminal and install the Base Kit on to that target Linux system using the appropriate Linux package manager.
    To get started, you need to install only the Base Kit on your WSL target; you can install additional oneAPI toolkits either now or at a later time.
  2. Configure your WSL Linux target so that the oneAPI development environment script ( runs when VS Code initiates a connection.
    Visual Studio Code does not currently provide a mechanism to automatically run scripts on your remote Linux target when it interacts with the WSL system (for example, running automatically). There are a variety of ways to get around this issue, only one of which is presented here. See the Bash Startup Files man page for more options.
    Add the following shell script lines to your remote Linux system’s /etc/profile script. This location (or in an /etc/profile.d/ script) will ensure that all users of your WSL target development system will run the environment script when they connect using Visual Studio Code:
    . /opt/intel/oneapi/ &>/dev/null
    The above assumes that you have installed your oneAPI toolkits on the WSL system in the default “root/sudo” installation location (/opt/intel/oneapi/). If you have installed the oneAPI tools in a different location on your remote Linux system, you will have to adjust the path to
    See Configure Your CPU or GPU System for more details regarding configuration of the oneAPI environment on a Linux system.

Configure Visual Studio Code on Your Local Host

You must install the VS Code “Remote - WSL” extension into your local copy of VS Code. This extension facilitates development on the WSL* system.
  1. Install the
    Remote - WSL
    extension by Microsoft. Click the
    icon and search for “remote wsl” in the search bar.
  2. Click
    . After installation, you see
    Remote – WSL
    in the
    Installed Extensions

Connect to Your WSL Linux System

See the Visual Studio Code Remote Development in WSL documentation for detailed instructions, requirements, and additional information.
  1. Open a WSL terminal for your desired Linux distribution. From within the terminal, invoke VS Code from the command line to start a local instance connected to WSL.
    user@host:~$ code
  2. A new VS Code window opens and is connected to the WSL system.
  3. Once connected, add the
    C/C++ extension
    to the VS Code instance. This extension is required to debug a remote session using the VS Code debug interface.

Explore Samples Using Visual Studio Code*

Before working with oneAPI samples, it is recommended that you install the VS Code “Sample Browser for Intel oneAPI Toolkits” extension and the VS Code “Environment Configurator for Intel oneAPI Toolkits” extension.
Both can be quickly found in the VS Code extensions marketplace by typing “oneapi” into the marketplace search bar.
The steps below describe how to use these extensions to configure the oneAPI development environment for use with VS Code and use the Sample Browser to locate and create sample projects that help you learn how to use oneAPI features.
To configure the oneAPI environment in VS Code:
  1. Press
    ( or
    View -> Command Palette…
    ) to open the Command Palette.
  2. Type
    Intel oneAPI
    to view options of the installed extensions.
  3. Click on
    Intel oneAPI: Initialize environment variables
  4. Locate the setvars file:
    • Linux: By default,
      is located in
      for root or sudo installations, or located in
      for local user installations.
    • Windows: By default,
      is located in
      C:\Program Files(x86)\Intel\oneAPI\
    If you customized the installation folder, setvars is in your custom folder.
  5. In the case of multiple folders in workspace, select the appropriate one. All tasks, launches, and terminals created from VS Code will now contain the oneAPI environment.
To browse oneAPI samples using VS Code:
  1. Click on the oneAPI button on the left navigation to view samples. If you do not have the extension installed, search the Extensions Marketplace for “Sample Browser for Intel oneAPI”.
  2. A list of available samples will open in the left navigation.
  1. To view the readme for the sample, click the image6 next to the sample. If you choose to build and run the sample, the readme will also be downloaded with the sample.
  2. To build and run a sample, click the foldericon to the right of the sample name.
  3. Create a new folder for the sample. The sample will load in a new window:
  4. Click to view instructions for the sample.
Not all oneAPI sample projects use CMake. The file for each sample specifies how to build the sample. We recommend that you check out the CMake extension for VS Code that is maintained by Microsoft.

Try Debugging (CPU and GPU Only) (Preview)

Intel® Distribution for GDB* does not currently support VS Code. You can use upstream gdb to debug.
This section assumes that you can build your sample and have installed the Microsoft VS Code C/C++ Extension. The C/C++ extension is required to configure the oneAPI C/C++ debugger.
The Intel® oneAPI Base Toolkit includes a special version of GNU* GDB (
) designed to support oneAPI C/C++ applications. To debug your DPC++ application using this special debugger, you will need to make changes to the .vscode/launch.json configuration file.
  1. Go to
    Open Configurations
    , and open the
    configuration settings.
    If you are prompted to select a debug environment, choose
    C++ (GDB/LLDB)
  2. Copy the code shown below into your launch.json file, and replace the
    property’s value with the path to your project’s executable (that is, the application that you are going to debug).
    If VS Code doesn’t recognize the application name, you may have to insert the full path and file name into the
  3. Add
    to your launch.json configuration’s
    application should have been added to your path when you ran to configure the oneAPI development environment, prior to starting VS Code. If you prefer, you can specify the full path and filename to the
    application in your launch.json file.
  4. In some configurations, GDB may not be compatible with VS Code. If this happens, add the environment variable to disable `gdb-oneapi` support for GPU autolaunch. This can either be done in the environment prior to launching VS Code, or within the launch.json:
    { "version":"0.2.0", "configurations":[ { "name":"(gdb) Launch", "type":"cppdbg", "request":"launch", "program":"${workspaceFolder}/build/array-transform", "args":[ "cpu" ], "stopAtEntry":false, "cwd": "${workspaceFolder}", "environment": [], "externalConsole":false, "MIMode":"gdb", "miDebuggerPath":"gdb-oneapi", "setupCommands":[ { "description":"Enable pretty-printing for gdb", "text":"-enable-pretty-printing", "ignoreFailures":true }, { "description": "Disable target async", "text": "set target-async off", "ignoreFailures": true } ] } ] }
  5. Bring up the debug view by selecting the
    icon in the
    Activity Bar
    . You can also use the keyboard shortcut (
  6. Start the run and debug session by clicking the green
    icon, or go to
    Start Debugging

Product and Performance Information


Performance varies by use, configuration and other factors. Learn more at