Skip to content

Latest commit

 

History

History
74 lines (56 loc) · 3.39 KB

README.md

File metadata and controls

74 lines (56 loc) · 3.39 KB
Raw

Spack package repo for Key4hep software packaging

This repository holds a set of Spack recipes for key4hep software.

Consult the the key4hep documentation website and the spack documentation for more details.

Spack Versions

The spack recipes in this repository should work with any recent version of spack (at least 0.20 is needed because they use the require keyword which was introduced in spack 0.20). The nightlies are currently built against the commit of spack that is in the .latest-commit file in this repository. From time to time the most recent commit is picked to get the latest version of the spack recipes. The commit of spack that was used to build a stack can be found in the file .spack-commit that is shipped with every stack on cvmfs.

Repository Contents

Apart from the recipes for key4hep packages in the folder packages, the repository contains a collection of environments used to build the stack in environments and some scripts used for publishing on cvmfs and other utilities in scripts. The builds run in Gitlab CI runners and the workflows can be found in the file .gitlab-ci.yml in the gitlab repository.

Additionally, the file .latest-commit contains the latest commit of Spack used for the recent builds, which is updated from time to time to keep up with the develop branch of Spack. In addition, the file .cherry-pick contains some fixes needed to build the stack. These can also be found in the file .cherry-pick that is shipped with every stack on cvmfs.

Central Installations

Installations of the software stack can be found under /cvmfs/sw.hsf.org (for CentOS 7) and /cvmfs/sw-nightlies.hsf.org (for CentOS 7, AlmaLinux 9 and Ubuntu) see:

https://key4hep.github.io/key4hep-doc/setup-and-getting-started/README.html

Requirements

To compile the key4hep stack some system packages are required; without these, the spack concretization or compilation can fail. The packages needed are an OpenGL implementation that can be installed:

yum install -y mesa-libGL mesa-libGL-devel mesa-libGLU mesa-libGLU-devel      # Centos 7
apt install -y libgl1-mesa-glx libgl1-mesa-dev libglu1-mesa libglu1-mesa-dev  # Ubuntu
dnf install -y mesa-libGL mesa-libGL-devel mesa-libGLU mesa-libGLU-devel      # AlmaLinux 9

The environments that make use of these libraries or headers expect them to be found under /usr, which is the typical location when they are installed system-wide (for example in /usr/include or /usr/lib).

Alternatively, one can install HEP_OSlibs, which will install the previous and more libraries.

In addition, for Ubuntu and Alma 9 the compilers are picked up from the system, so, for example, building in an image without gcc or glibc won't work. These commands should install most of the compilers and the development tools:

apt install -y build-essential gfortran                            # Ubuntu
dnf groupinstall -y "Development Tools" && dnf install -y gfortran # AlmaLinux 9

Dockerfiles with the images that are used to build the key4hep stack can be found in https://github.com/key4hep/key4hep-images.