---
# System prepended metadata

title: Goals for ICON build system and package managing development within EXCLAIM

---

# Goals for ICON build system and package managing development within EXCLAIM

* Building icon-nwp on alps
    * Server-specific build information should only be given in one place (ideally spack upstream provided by CSCS)
    * Server-specific runtime information not solved!
    * Separating build system and package manager as cleanly as possible
    
* Cmake + spack build of ICON
    * Inspired by cmake build of ICON ART during a hackathon
    * Should separate build system from package manager
    * Why cmake? More cmake experts than autotools experts around.
    * external submodules become spack packages

* Building icon-exclaim (on alps)
    * Py-gt4py and py-icon4py and icon-exclaim spack dependency discussion

* Current issue with packaging
    * not clear how to best combine spack and python : 
        * concretization problems sometimes
    * developer workflow needed: don't want to recompile everything when changing one stencil

* Building of icon software in the icon community
    * Main contact Sergey Kosukhin
    * Some ongoing work to use cmake for the new libraries, see e.g. https://gitlab.dkrz.de/icon-libraries/libfortran-support


Tasks:
* Make spack build of icon-nwp work for new alps based on MCH work on balfrin (C2SM) (spack + autotools)
* Finalize cmake demonstration build of ICON and 
    * show it to ICON community (Sergey)
    * Push for introducing cmake build in ICON community
* Discuss spack + pip problem
* Discuss development workflow problems
    * work on all 3 projects at the same time
    * what if stencil is not in one file