Developer Guide

Generating Umpire host-config files


This is optional if you are on LC machines, since some host-config files have already been generated (at least for Quartz and Lassen) and can be found in the host-configs repository directory.

Umpire only directly depends on CMake. However, this mechanism will generate a cmake configuration file that reproduces the configuration Spack <> would have generated in the same context. It contains all the information necessary to build Umpire.

In particular, the host config file will setup: * flags corresponding with the target required (Release, Debug). * compilers path, and other toolkits (cuda if required), etc.

This provides an easy way to build Umpire based on Spack <> and encapsulated in Uberenv.

Uberenv role

Uberenv helps by doing the following:

  • Pulls a blessed version of Spack locally

  • If you are on a known operating system (like TOSS3), we have defined compilers and system packages so you don’t have to rebuild the world (CMake typically in Umpire).

  • Overrides Umpire Spack packages with the local one if it exists. (see scripts/uberenv/packages).

  • Covers both dependencies and project build in one command.

Uberenv will create a directory uberenv_libs containing a Spack instance with the required Umpire dependencies installed. It then generates a host-config file (<config_dependent_name>.cmake) at the root of Umpire repository.

Using Uberenv to generate the host-config file

$ python scripts/uberenv/


On LC machines, it is good practice to do the build step in parallel on a compute node. Here is an example command: srun -ppdebug -N1 --exclusive python scripts/uberenv/

Unless otherwise specified Spack will default to a compiler. It is recommended to specify which compiler to use: add the compiler spec to the --spec Uberenv command line option.

On blessed systems, compiler specs can be found in the Spack compiler files in our repository: scripts/uberenv/spack_configs/<System type>/compilers.yaml.

Some examples uberenv options:

  • --spec=%clang@4.0.0

  • --spec=%clang@4.0.0+cuda

  • --prefix=<Path to uberenv build directory (defaults to ./uberenv_libs)>

Building dependencies can take a long time. If you already have a spack instance you would like to reuse (in supplement of the local one managed by Uberenv), you can do so changing the uberenv command as follow:

$ python scripts/uberenv/ --upstream=</path/to/my/spack>/opt/spack

Using host-config files to build RAJA

When a host-config file exists for the desired machine and toolchain, it can easily be used in the CMake build process:

If I need to build Umpire with _clang_ on _lassen_, I can see there is already a host-config file named lassen-blueos_3_ppc64le_ib_p9-clang@9.0.0.cmake. To use it (on lassen):

$ mkdir build && cd build
$ cmake -C ../host-configs/lassen-blueos_3_ppc64le_ib_p9-clang@9.0.0.cmake ..
$ cmake --build -j .
$ ctest --output-on-failure -T test


This will build the default configuration. Not all parameters are embedded into the host-config file. For example, producing C/Fortran APIs, using OppenMP, enabling tests, is to be configured on command line.