---
# System prepended metadata

title: Spack build of ICON-EXCLAIM

---

**Spack build of ICON-EXCLAIM**

**Meeting 17.12.2024**

Proposition to split the build of the python packages when using spack for ICON-EXCLAIM using pip or spack depending on their dependencies/complexity
Let’s discuss how this could look like

In order to avoid conflict or use of different/incompatible underlying libraries the python interpreter itself need to be build with spack


Build icon-exclaim with spack
Build icon4py with spack
Build pure python package, those with no compilation, should be installed with pip
Pyhton package which require compilatoin, e.g. mpi, ... : mpi




How would this work:
Load spack env.
Then pip install
Need to figure out how to do have the correct runtime package env.


Building

Create spack env that contains a python venv


**Proposition**

1. keep current approach
2. transit to Granule
3. get icon-exclaim to compile with spack with the current approach
4. Evaluate new approach with pip and spack

**Issue to consider**
- make sure pip and spack do not install different versions of package


**Other idea**
- Inject the path of the python installations as a variant
