..
   Copyright Spack Project Developers. See COPYRIGHT file for details.

   SPDX-License-Identifier: (Apache-2.0 OR MIT)

.. meta::
   :description lang=en:
      A guide to using the Intel oneAPI packages in Spack, including how to build with icx, use the oneAPI Spack environment, and configure externally installed oneAPI tools.

.. _inteloneapipackage:


IntelOneapi
===========


Spack can install and use the Intel oneAPI products.
You may either use Spack to install the oneAPI tools or use the `Intel installers`_.
After installation, you may use the tools directly, or use Spack to build packages with the tools.

The Spack Python class ``IntelOneapiPackage`` is a base class that is used by ``IntelOneapiCompilers``, ``IntelOneapiMkl``, ``IntelOneapiTbb`` and other classes to implement the oneAPI packages.
Search for ``oneAPI`` at `packages.spack.io <https://packages.spack.io>`_ for the full list of available oneAPI packages, or use:

.. code-block:: console

   $ spack list -d oneAPI

For more information on a specific package, do:

.. code-block:: console

   $ spack info --all <package-name>


Building a Package With icx
---------------------------

In this example, we build patchelf with ``icc`` and ``icx``.
The compilers are installed with Spack.

Install the oneAPI compilers:

.. code-block:: spec

   $ spack install intel-oneapi-compilers


To build the ``patchelf`` Spack package with ``icx``, do:

.. code-block:: spec

   $ spack install patchelf%oneapi


Using oneAPI Spack environment
-------------------------------

In this example, we build LAMMPS with ``icx`` using Spack environment for oneAPI packages created by Intel.
The compilers are installed with Spack like in example above.

Install the oneAPI compilers:

.. code-block:: spec

   $ spack install intel-oneapi-compilers

Clone `spack-configs <https://github.com/spack/spack-configs>`_ repo and activate Intel oneAPI CPU environment:

.. code-block:: console

   $ git clone https://github.com/spack/spack-configs
   $ spack env activate spack-configs/INTEL/CPU
   $ spack concretize -f

`Intel oneAPI CPU environment <https://github.com/spack/spack-configs/blob/main/INTEL/CPU/spack.yaml>`_  contains applications tested and validated by Intel.
This list is constantly extended.
Currently, it supports:

- `Devito <https://www.devitoproject.org/>`_
- `GROMACS <https://www.gromacs.org/>`_
- `HPCG <https://www.hpcg-benchmark.org/>`_
- `HPL <https://netlib.org/benchmark/hpl/>`_
- `LAMMPS <https://www.lammps.org/#gsc.tab=0>`_
- `OpenFOAM <https://www.openfoam.com/>`_
- `Quantum Espresso <https://www.quantum-espresso.org/>`_
- `STREAM <https://www.cs.virginia.edu/stream/>`_
- `WRF <https://github.com/wrf-model/WRF>`_

To build LAMMPS with oneAPI compiler from this environment just run:

.. code-block:: spec

   $ spack install lammps

Compiled binaries can be found using:

.. code-block:: console

   $ spack cd -i lammps

You can do the same for all other applications from this environment.


Using oneAPI MPI to Satisfy a Virtual Dependence
------------------------------------------------

The ``hdf5`` package works with any compatible MPI implementation.
To build ``hdf5`` with Intel oneAPI MPI do:

.. code-block:: spec

   $ spack install hdf5 +mpi ^intel-oneapi-mpi

Using Externally Installed oneAPI Tools
---------------------------------------

Spack can also use oneAPI tools that are manually installed with `Intel Installers`_.
The procedures for configuring Spack to use external compilers and libraries are different.

Compilers
^^^^^^^^^

To use the compilers, add some information about the installation to ``packages.yaml``.
For most users, it is sufficient to do:

.. code-block:: console

   $ spack compiler add /opt/intel/oneapi/compiler/latest/bin

Adapt the paths above if you did not install the tools in the default location.
After adding the compilers, using them is the same as if you had installed the ``intel-oneapi-compilers`` package.
Another option is to manually add the configuration to ``packages.yaml`` as described in :ref:`Compiler configuration <compiler-config>`.

Before 2024, the directory structure was different:

.. code-block:: console
  
  $ spack compiler add /opt/intel/oneapi/compiler/latest/linux/bin/intel64
  $ spack compiler add /opt/intel/oneapi/compiler/latest/linux/bin


Libraries
^^^^^^^^^

If you want Spack to use oneMKL that you have installed without Spack in the default location, then add the following to ``~/.spack/packages.yaml``, adjusting the version as appropriate:

.. code-block:: yaml

   intel-oneapi-mkl:
     externals:
     - spec: intel-oneapi-mkl@2021.1.1
       prefix: /opt/intel/oneapi/


Using oneAPI Tools Installed by Spack
-------------------------------------

Spack can be a convenient way to install and configure compilers and libraries, even if you do not intend to build a Spack package.
If you want to build a Makefile project using Spack-installed oneAPI compilers, then use Spack to configure your environment:

.. code-block:: spec

   $ spack load intel-oneapi-compilers

And then you can build with:

.. code-block:: console

   $ CXX=icpx make

You can also use Spack-installed libraries.
For example:

.. code-block:: spec

   $ spack load intel-oneapi-mkl

This updates your environment CPATH, LIBRARY_PATH, and other environment variables for building an application with oneMKL.


.. _`Intel installers`: https://software.intel.com/content/www/us/en/develop/documentation/installation-guide-for-intel-oneapi-toolkits-linux/top.html
