kgerheiser
commented
2 years ago On a local machine, I think the steps should be spack compiler find, spack external find. Leave it at the default of only finding build tools and maybe some specific externals. Several of the workarounds in the CI are external packages on macOS (sqlite, m4, and some more). Then, set compiler/mpi. Should also have the ability to build MPI with Spack. Meta-module generation is disabled for internal MPI. I'm n
Adding packages: spack add <spec> or manually edit spack.yaml to include a spec. Talk about spec syntax and default variants/versions.
Chaining environments by setting upstreams. Provide pre-configured environments HPC systems that have upstreams configured?
Perhaps related to putting the documentation into Read the Docs instead of spread across several READMEs?
climbfuji
I am still not sure how to tell users (they were all macOS users) to adapt their default site configs to work.
I had to walk all testers through this:
README.mdand install brew packages, configure PythonREADME.md: a. Create default site config b. Runspack external find ...andspack compiler find ...README.md. Use a graphical diff tool to compare to the macos reference site config to figure out which packages to remove (for example, macOS native sqlite which doesn't have the dev. headers, but there are more) and to add (e.g. qt5 - this could be improved by updating the qtpackage.py), setpackages:all::compilersandpackages:all::mpi, ...README.md: concretize, install, create modules, create meta modulesDocumentation is still missing: