Get Started

  • 2022.3
  • 09/08/2022
  • Public Content

Build and Run a Sample Project Using the
Visual Studio*
Command Line

Intel® oneAPI HPC Toolkit
If you have not already configured your development environment, go to Configure Your System then return to this page. If you have already completed the steps to configure your system, continue with the steps below.
Command line development can be done with a terminal window or done through Visual Studio Code*. Some tasks can be automated using extensions. To learn more, see Using Visual Studio Code with Intel® oneAPI Toolkits.
To compile and run a sample:
  1. Download the sample using the oneAPI CLI Samples Browser.
  2. Compile and run the sample with
    Microsoft Build*

Download Samples using the oneAPI CLI Samples Browser

Use the oneAPI CLI Samples Browser to browse the collection of online oneAPI samples. As you browse the oneAPI samples, you can copy them to your local disk as buildable sample projects. Most oneAPI sample projects are built using Make or CMake, so the build instructions are included as part of the sample in a README file. The oneAPI CLI utility is a single-file, stand-alone executable that has no dependencies on dynamic runtime libraries.
An internet connection is required to download the samples for oneAPI toolkits. For information on how to use this toolkit offline, see Developing with Offline Systems in the Troubleshooting section.
If you develop using Visual Studio Code*, some tasks can be automated with extensions. To learn more, see Using Visual Studio Code with Intel® oneAPI Toolkits.
To watch a video presentation of how to create a project with the command line, see Exploring Intel® oneAPI Samples from the Command Line.
The oneAPI CLI Samples Browser does not work with system proxy settings and does not support WPAD proxy. If you have trouble connecting from behind a proxy, please see Troubleshooting.
  1. Open a
  2. Set
    system variables by
    "C:\Program Files (x86)\Intel\oneAPI\setvars.bat"
    For Windows PowerShell* users, execute this command:
    cmd.exe "/K" '"C:\Program Files (x86)\Intel\oneAPI\setvars.bat" && powershell'
    The command above assumes you installed to the default folder. If you customized the installation folder,
    is in your custom folder.
    script can be managed using a configuration file, which is especially helpful if you need to initialize specific versions of libraries or the compiler, rather than defaulting to the "latest" version. For more details, see Using a Configuration File to Manage Setvars.bat.
    oneAPI Development Environment Setup for more configuration options.
  3. In the same
    window, run the application :
    The oneAPI CLI menu appears:
  4. Move the arrow key down to select
    Create a project
    , then press
    . The language selection will appear. If you installed
    Intel® oneAPI Base Toolkit
    , but you want to work with the
    Intel® oneAPI HPC Toolkit
    and samples, ensure the HPC toolkit is installed. If it is not installed, install the HPC toolkit, then return to step 1 of this procedure.
  5. Select the language for your sample. For your first project, select
    , then press
    . The toolkit samples list appears.
  6. Select the
    Matrix Mul
    sample which appears at the top of the list:
  7. After you select a sample, press
  8. Specify the location for the project. The default location includes the path from where the utility was run and the name of the project.
  9. Press
    to select Create, then press
Now that you have the samples downloaded, compile and run the sample with

Build and Run a Sample Using Microsoft Build*

  1. Using the same command prompt window where you ran
    , navigate to the folder where you downloaded the samples.
  2. Build the program:
    MSBuild matrix_mul_dpcpp.sln /t:Rebuild /p:Configuration="Release"
  3. Navigate to the Release folder (example:
  4. Run the program:
message will appear.

See Explore SYCL* Through Samples to learn more.

Product and Performance Information


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