Get Started with the Intel® oneAPI Rendering Toolkit for macOS*

ID 766440
Date 3/31/2023
Public

A newer version of this document is available. Customers should click here to go to the newest version.

Build and Run Sample Projects Using the Command Line

Prerequisite: Configure your system.

To build and run a sample:

  1. Locate a sample project using the Code Sample Browser for Intel® oneAPI Toolkits.
    NOTE:
    Alternatively, advanced users can acquire the source code with Git* from the oneAPI-samples repository:
    git clone https://github.com/oneapi-src/oneAPI-samples.git
    cd oneAPI-samples/RenderingToolkit/GettingStarted
  2. Build and run a sample project using CMake*.

Download Samples using the Code Sample Browser for Intel® oneAPI Toolkits

Use the Code Sample Browser for Intel oneAPI Toolkits to browse the collection of online Intel® oneAPI samples. You can copy the samples to your local disk as buildable sample projects. Most Intel oneAPI sample projects are built using Make* or CMake, so the build instructions are included as part of the sample in a README file. Code Sample Browser for Intel oneAPI Toolkits is a stand-alone single-file executable that has no dependencies on dynamic runtime libraries.

For a list of components that support CMake, see Use CMake with oneAPI Applications. All Render Kit samples use CMake.

IMPORTANT:

An internet connection is required to download the samples for Intel oneAPI Toolkits. For information on how to use this toolkit offline, see Developing in Offline Systems.

To download the Intel® oneAPI Rendering Toolkit (Render Kit) samples:

  1. Open a new terminal.
  2. If you did not set up Intel oneAPI Toolkit environment permanently: Set up environment variables:
    • For root or sudo users:
      . /opt/intel/oneapi/setvars.sh
    • For non-root users:
      . ~/intel/oneapi/setvars.sh

    See Set up Environment Variables for other options.

    NOTE:
    If you installed the Render Kit to a custom location, make sure to replace /opt/intel/oneapi/ (for root or sudo users) or ~/intel/oneapi/ (for non-root users) with the custom installation path before running the command.
  3. If you are behind proxy, you may need to configure your proxy:
    export http_proxy=http://<user>:<pass>@proxy.<server>.com:<port>
    export https_proxy=http://<user>:<pass>@proxy.<server>.com:<port>
  4. From the terminal, run the Code Sample Browser for Intel oneAPI Toolkits with C++ and C samples.
    oneapi-cli -l cpp,c

    The oneAPI CLI menu appears:

  5. Select Create a project using arrow keys, then press Enter.

    The language selection will appear.

  6. Select the language for your sample. For your first project, select cpp, then press Enter.

    The toolkit samples list appears. Render Kit samples are located underneath the oneAPI Libraries subtree.

  7. Navigate to oneAPI Libraries > OSPRay > Intel OSPRay Getting Started, then press Enter.
    NOTE:
    Some Intel oneAPI samples might not be available on macOS*.
  8. Specify a location to download the project to. By default, it is the path from where you ran the Code Sample Browser for Intel oneAPI Toolkits and project name. Intel OSPRay Getting Started by default extracts to a folder name of 01_ospray_gsg

  9. Press Tab to select Create, then press Enter.
  10. Repeat the steps to download samples for other components: oneAPI Libraries > Embree > Intel Embree Getting Started (02_embree_gsg) for Intel® Embree, oneAPI Libraries > Open Image Denoise > Intel Open Image Denoise Getting Started (04_oidn_gsg, 03 is located elsewhere) for Intel® Open Image Denoise, and oneAPI Libraries > ISPC > Intel Implicit SPMD Program Compiler Getting Started (05_ispc_gsg) for Intel® Implicit SPMD Program Compiler (Intel® ISPC). The samples are numbered and staged to be tried in order.

    Intel Open Volume Kernel Library 03_openvkl_gsg sample is available in the C language menu option of the Code Sample Browser for Intel oneAPI Toolkits:

    1. Select c language:

    2. Select the Intel Open VKL sample oneAPI Libraries > Open VKL > Intel Open VKL Getting Started:

See Exploring Intel oneAPI Samples from the Command Line for a video tutorial on creating a project with the command line.

Build and Run an Intel® OSPRay Sample using CMake*

  1. Navigate to the folder where you downloaded the 01_ospray_gsg sample.
  2. Run the following commands to build the sample:
    mkdir build
    cd build
    cmake ..
    cmake --build .
  3. Run the application.
    ./ospTutorialCpp
  4. Review the output images with an image viewer application for PPM file type. For example, with Preview:
    open firstFrameCpp.ppm
    open accumulatedFrameCpp.ppm

    You should see the output images:

    • Single-accumulation render firstFrameCpp:

    • Ten-accumulation render accumulatedFrameCpp:

Build and Run an Intel® Embree Sample using CMake*

  1. Navigate to the folder where you downloaded the 02_embree_gsg sample.
  2. Run the following commands to build the sample:
    mkdir build
    cd build
    cmake ..
    cmake --build .
  3. Run the application.
    ./minimal

    The sample application performs two ray-to-triangle intersect tests with the Intel Embree API. One test is successful, while the other test is a miss. Output is written to the terminal:

    0.000000, 0.000000, -1.000000: Found intersection on geometry 0, primitive 0 at tfar=1.000000
    1.000000, 1.000000, -1.000000: Did not find any intersection.

Build and Run an Intel® Open Volume Kernel Library Sample using CMake*

  1. Navigate to the folder where you downloaded the03_openvkl_gsg sample.
  2. Run the following commands to build the sample:
    mkdir build
    cd build
    cmake ..
    cmake --build .
  3. Run the application.
    ./vklTutorial

    The sample application shows sampling within a procedurally generated volume and outputs. Sampling, gradient computation, and multi-attribute sampling. Output is written to the terminal.

Build and Run an Intel® Open Image Denoise Sample using CMake*

  1. Navigate to the folder where you downloaded the 04_oidn_gsg sample.
  2. Run the following commands to build the sample:
    mkdir build
    cd build
    cmake ..
    cmake --build .
  3. Convert the accumulatedFrameCpp.ppm image to PFM format with LSB data ordering. For example, with the ImageMagick* convert tool:
    <path-to-ImageMagick>/convert <path-to-sample>/01_ospray_gsg/build/accumulatedFrameCpp.ppm -endian LSB PFM:accumulatedFrameCpp.pfm
    NOTE:
    If you installed ImageMagick with Homebrew*, the <path-to-ImageMagick> is typically /usr/local/Cellar/imagemagick/<version>/bin.
  4. Run the application to denoise the image.
    ./oidnDenoise -hdr accumulatedFrameCpp.pfm -o denoised.pfm
  5. Review the output image with an image viewer application for PPM file type. For example, with Preview:
    open denoised.pfm
    • Original ten-accumulation render accumulatedFrameCpp:

    • Denoised result denoised.pfm:

Build and Run an Intel® Implicit SPMD Program Compiler Sample using CMake*

  1. Navigate to the folder where you downloaded the 05_ispc_gsg sample.
  2. Run the following commands to build the sample:
    mkdir build
    cd build
    cmake ..
    cmake --build .
  3. Run a single-target sample application:
    ./simple
  4. Run a multi-target sample application:

    The application executes a floating-point array arithmetic operation. The result is printed to stdout. Both applications emit the same results:

    0: simple(0.000000) = 0.000000
    1: simple(1.000000) = 1.000000
    2: simple(2.000000) = 4.000000
    3: simple(3.000000) = 1.732051
    4: simple(4.000000) = 2.000000
    5: simple(5.000000) = 2.236068
    6: simple(6.000000) = 2.449490
    7: simple(7.000000) = 2.645751
    8: simple(8.000000) = 2.828427
    9: simple(9.000000) = 3.000000
    10: simple(10.000000) = 3.162278
    11: simple(11.000000) = 3.316625
    12: simple(12.000000) = 3.464102
    13: simple(13.000000) = 3.605551
    14: simple(14.000000) = 3.741657
    15: simple(15.000000) = 3.872983

Build and Run an Intel® Open PGL Sample using CMake*

  1. Navigate to any new writable and empty folder:
    cd /home/${USER}
    mkdir pgl_gsg
    cd pgl_gsg
  2. Create a new file, opengl_check.cpp, using a raw text editor (notepad etc.). Save the below contents into the file:
    #include <iostream>
    
    #include <openpgl/cpp/OpenPGL.h>
    
    int main(int argc, char *argv[]) {
    
    openpgl::cpp::Device device(PGL_DEVICE_TYPE_CPU_4);
    
    PGLFieldArguments fieldArgs;
    
    pglFieldArgumentsSetDefaults(fieldArgs, PGL_SPATIAL_STRUCTURE_KDTREE,
    
    PGL_DIRECTIONAL_DISTRIBUTION_PARALLAX_AWARE_VMM);
    
    openpgl::cpp::Field field(&device, fieldArgs);
    
    std::cout << "Field created successfully... exiting\n";
    
    return 0;
    
    }
  3. Create a new file, CMakeLists.txt, using a raw text editor (notepad etc.). Save the below contents into the file:
    cmake_minimum_required(VERSION 3.1)
    
    project(openpgl_check LANGUAGES CXX)
    
    include_directories("$ENV{ONEAPI_ROOT}/openpgl/latest/include")
    
    link_directories("$ENV{ONEAPI_ROOT}/openpgl/latest/lib")
    
    add_executable(openpgl_check openpgl_check.cpp)
    
    target_link_libraries(openpgl_check PRIVATE openpgl)
  4. Run the following commands to build the sample:
    mkdir build
    cd build
    cmake ..
    cmake --build . 
  5. Run the check application:
    ./openpgl_check
  6. If you see the below output without error, you have successfully built and runtime linked to the Intel® Open PGL library:
    Field created successfully... exiting

Next Steps

All samples have detailed README.md instructions for further review. Next, try running pre-compiled sample applications included with the toolkit OR explore additional resources in Next Steps.