Corporate network users: Ensure package management tools (for example, apt) can connect through your proxy servers if necessary. Set the following variables to configure your proxy:
export http_proxy=http://<user>:<pass>@proxy.<server>.com:<port>
export https_proxy=https://<user>:<pass>@proxy.<server>.com:<port>
export HTTP_PROXY=${http_proxy}
export HTTPS_PROXY=${https_proxy}
Optional: If you want to run the build programs or run samples from a Docker* container, proceed with step 2. Otherwise, skip to step 3:
Install Docker:
sudo -E apt update
sudo -E apt install docker.io
Give a Docker session access to a window manager using Xhost*:
xhost +
Without the Xhost, GUI-based Intel oneAPI Rendering Toolkit samples launched from the Docker can give
X11: Failed to open display
error.
Run the Docker and work from a container:
If you have proxy set up:

sudo -E docker run --name renderkit --rm -it --privileged -e DISPLAY=$DISPLAY -v /tmp/.X11-unix:/tmp/.X11-unix -e HTTP_PROXY=$HTTP_PROXY -e HTTPS_PROXY=$HTTPS_PROXY -e http_proxy=$http_proxy -e https_proxy=$https_proxy ubuntu bash

If you do not have proxy set up:

sudo -E docker run --name renderkit --rm -it --privileged -e DISPLAY=$DISPLAY -v /tmp/.X11-unix:/tmp/.X11-unix ubuntu bash
In the Docker container, install sudo for convenience:
apt update
apt install sudo
In the Docker container, install CPIO* and
ncurses-term
to support Intel oneAPI Rendering Toolkit installation:
apt install cpio ncurses-term
Copy your chosen
Render Kit
installation files to the Docker container. Launch a new host terminal and copy the installer to your container. For example, if you have the offline installer downloaded, replace the
<version>
with your Render Kit version and run the following from the host terminal:
sudo docker container ls
sudo docker cp ~/Downloads/l_RenderKit_<version>_offline.sh <your_container_id>:/.
In the Docker container, install the
Intel® oneAPI Rendering Toolkit
:
Recommended:
Use the
opt-in
option when installing the toolkit to send usage statistics. The statistics helps Intel maintain the product.
./l_RenderKit_<version>_offline.sh
For additional installation instructions, refer to the Installation Guide for Intel® oneAPI Toolkits.
Run all the steps below from your Docker container.
Install dependencies for building and running samples:
Install pkg-config, GNU* Development Tools, and the Kitware* repository dependencies.
sudo -E apt install apt-transport-https ca-certificates gnupg software-properties-common wget pkg-config build-essential
Install the latest CMake* from the Kitware repository for your OS distribution, See full instruction at the Kitware APT Repository. For example, for Ubuntu OS 20.04:
Check your OS distribution. For Ubuntu OS 20.04, it reports

Focal Fossa

.

cat /etc/*release

Add the repository to your sources and update:

wget -O - https://apt.kitware.com/keys/kitware-archive-latest.asc 2>/dev/null | gpg --dearmor - | sudo tee /etc/apt/trusted.gpg.d/kitware.gpg >/dev/null

sudo -E apt-add-repository 'deb https://apt.kitware.com/ubuntu/ focal main'

sudo -E apt update

sudo -E apt info cmake

Install CMake:

sudo -E apt -y install cmake
If you already have the CMake installed, the Kitware version may conflict on updated dependencies. If your version of CMake is not from the Kitware repository, you can run the following to remove the conflicting version and reinstall:
apt purge cmake
Some OS distributions use older versions CMake that do not work with the Intel oneAPI Rendering Toolkit. Skip this step if you want to keep your version of CMake.
Note the following:
Although
the CMake and pkg-config build tools are
not required by the oneAPI tools and toolkits, many oneAPI samples are provided as CMake projects and require CMake to build them.
In some cases pkg-config is necessary to locate libraries needed to complete a build of the application.
Expected compiler toolchains access GNU Development Tools to provide a complete C/C++ development environment. If your distribution of Linux does not include the complete suite of GNU development tools, you need to install these tools. In the commands above, GNU development tools are installed with the
build-essentials
package. The
Render Kit
is validated with compilers that support C99 and C++11.
Install Mozilla Firefox*, Grip*, Evince*, Eye of GNOME* image viewer, Git*, and ImageMagick*:
sudo -E apt update
sudo -E apt install git eog grip evince firefox imagemagick
The installation of the GUI applications above applies GUI support libraries that enable advanced tutorials to run. Use these applications to:
Mozilla Firefox, Grip*, and Evince* to review advanced sample usage instructions
A
.ppm
image viewer (for example, Image Magick, Eye of GNOME or GIMP*) to open result images
Git to get the samples
Install the GLU and the imaging libraries:
sudo -E apt install libpng-dev libpng16-16 libjpeg-turbo8-dev libjpeg-turbo8 libglfw3 libglfw3-dev  libglu1-mesa libopenimageio-dev libopenimageio-doc libopenimageio2.1
In the repository, the
libopenimageio
can be a different version for your OS distribution.
dev
-suffixed packages are used for building, while non-
dev
packages are used at application run time.

sudo yum update
sudo yum -y install cmake pkgconfig
sudo yum groupinstall "Development Tools"

sudo zypper update
sudo zypper --non-interactive install cmake pkg-config
sudo zypper --non-interactive install pattern devel_C_C++

which cmake pkg-config make gcc g++

source <install-dir>/setvars.sh

For Intel® OSPRay:
/opt/intel/oneapi/ospray/latest/env/vars.sh
For Intel® Embree:
/opt/intel/oneapi/embree/latest/env/vars.sh
For Intel® Open Image Denoise:
/opt/intel/oneapi/oidn/latest/env/vars.sh
For Intel® Open Volume Kernel Library (Intel® Open VKL):
/opt/intel/oneapi/openvkl/latest/env/vars.sh
For Intel® OSPRay Studio:
/opt/intel/oneapi/ospray_studio/latest/env/vars.sh

source /opt/intel/oneapi/embree/latest/env/vars.sh

To have the environment automatically set up for all projects, add a
source <install_dir>/<component_dir>/latest/env/vars.sh
component-specific command to a startup script where it will be invoked automatically. Replace
<install_dir>
with the path to your oneAPI install location and
<component_dir>
to the directory name for a specific component.
For example, you can add the
source <install_dir>/<component_dir>/latest/env/vars.sh
command to your
~/.bashrc
,
~/.bashrc_profile
, or
~/.profile
file.
To make the settings permanent for all accounts on your system, create a one-line
.sh
script in your system's
/etc/profile.d
folder that sources
vars.sh
(for more details, see /etc/profile.d/).

Build your programs with the
rpath
set similarly or to the local directory.
Stage the desired version of the
oneTBB
runtime libraries along with resulting executables to disambiguate distributions of the
oneTBB
installed on the system.