Build and Run a Sample Project Using the
Command Line
Intel® oneAPI Base 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:
- Locate a sample project using the oneAPI CLI Samples Browser.
- Build and run a sample project usingMake* or CMake*.
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.
To see a list of components that support CMake, see
Use CMake to with oneAPI Applications .
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.
To watch a video presentation of how to create a project with the command line, see
Exploring Intel® oneAPI Samples from the Command Line.
- Open aterminalwindow.
- If you did not complete the steps in Option 2: One time set up for setvars.sh in the Configure Your System section,setsystem variables bysourcingsetvars:For system wide installations (requires root or sudo privileges):. /opt/intel/oneapi/setvars.shThe command above assumes you installed to the default folder. If you customized the installation folder,For private installations:. ~/intel/oneapi/setvars.shsetvars.shis in your custom folder.Thesetvars.shscript 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.sh.If you need to setup the environment in a non-POSIX shell, seeoneAPI Development Environment Setup for more configuration options.
- In the sameterminalwindow, run the application(it should be in your PATH):The oneAPI CLI menu appears:oneapi-cli
- Use the up and down arrow keys to selectCreate a project, then pressEnter
- Move the arrow key down to selectCreate a project, then pressEnter. The language selection will appear. If you want to run samples from a toolkit other than theIntel® oneAPI Base Toolkit, install the domain-specific toolkit before proceeding.
- Select the language for your sample. For your first project, selectcpp, then pressEnter. The toolkit samples list appears.
- Select theVector Addsample. Vector Add is a simple test application that will help verify that the tools are setup correctly and can access your system's GPU:
- After you select a sample, pressEnter.
- Specify the location for the project. The default location includes the path from where the utility was run and the name of the project.
- PressTabto select Create, then pressEnter:
Build and Run a Project Based on a oneAPI Sample Using Make
Some samples require additional steps or arguments for building and/or running the sample. Review the sample's
README.md
file for specific details regarding how to build and run the sample.
- Open a command prompt.
- Navigate to the directory which you specified when creating (downloading) the project. If there is no makefile in the project, refer to the section below on how to use CMake to create a project with a makefile that you can use to run the design.
- Build the program using Make.cd vector-add make all
- Run the program.make run
- Clean the program.make clean
Build and Run a Project Based on a oneAPI Sample using CMake
Some samples require additional steps or arguments for building and/or running the sample. Review the sample's
README.md
file for specific details regarding how to build and run the sample.
Vector add can only be run with Make. To run a different sample using CMake, where
<sample_name>
is the name of the sample you want to run.
To find a sample that uses CMake, browse the
oneAPI Samples GitHub repository and view the
README
file for each sample to see if the sample can be run with CMake.
- If necessary, re-run the command-line utility and select a CMake project that contains aCMakeLists.txtfile.cd <sample_name>
- Navigate to the build directory.mkdir build cd build
- Build the program. Run CMake in the build directory to create the makefile. Use the newly created makefile to build the executable.cmake ../. make VERBOSE=1
- Run the program.make run
- Clean the program.make clean
Compile and run a sample for FPGA
You can run the
vector-add
sample (or any FPGA SYCL code) in the following modes:
- Emulation:Verifies the code correctness. Compilation completes in few seconds. Use this mode if you are using theIntel® oneAPI Base Toolkit
- Report:Generates a static optimization report for design analysis. Compilation can take a few minutes to complete. When completed, you can find the reports in<project_name>.prj/reports/report.html. This can be used with theIntel® oneAPI Base Toolkit. For more information about the reports, refer to the FPGA Optimization Guide for Intel® oneAPI Toolkits.
- Hardware:Generates the actual bitstream on an FPGA device. Compilation can take few hours to complete. Use this mode to measure performance. To use this mode, download the Intel® Quartus® Prime Pro Edition software and BSPs separately. For more information, refer to the Install Software for Intel® FPGA Development Flow section in theIntel® oneAPI Toolkits Installation Guide for Linux* OSand Intel® FPGA Add-On for oneAPI Base Toolkit web page.
After downloading the
vector-add
design example using the oneAPI CLI Samples Browser, perform the following steps to compile and run the design:
- Change to the directory containing thevector-adddesign example using:cd <vector-add directory on the same system>
- Run the followingmake cleancommand before you start compiling.make clean -f Makefile.fpga
- Compile the design using one of the following options:
- Compile for emulation using:make fpga_emu -f Makefile.fpga
- Compile the report using:make report -f Makefile.fpgaYou can view the report atvector-add_report.prj/reports/report.html. This does not generate an executable.
- Compile for hardware (takes a longer duration to complete) using:make hw -f Makefile.fpga
If you compiled the hardware on a development system, copy the executable filevector-add.fpgato the runtime system. - Run the design using one of the following options:
- Run the design for emulation using:make run_emu -f Makefile.fpgaIf you are using a separate development system, perform this step on that system.
- Run the design on FPGA hardware using:make run_hw -f Makefile.fpga
To understand the command used in the Makefile, refer to the Intel® oneAPI Programming Guide.
See
Explore SYCL* Through Samples to learn more.