[EPIC]: Transition to spack. Deprecate thirdPartyLibs
Open
Nobody has claimed this yet.
EPIC
type: documentation
type: feature
- Dominant language
- C++
- Stars
- 287
- Forks
- 109
- Avg merge
- 4d 41m
- Merged PRs (30d)
- 5
Description
What is the requested feature?
It is time to say farewell to our thirdPartyLibs repository, and the cmake build system for our TPL's. We have a viable spack configuration setup, so we should finish it up and proceed with the transition. Steps:
- Get spack config working for our target platforms on LC (@bmhan12),...
- and Pangea2, pangea3, pecan, etc (@TotoGaz)
- Develop TPL deployment strategy to replicate what is currently done. i.e. when the
thirdPartyLibsare built, then are sent up to dockerhub for use with the main repo CI...and they are deployed to Total systems. I think this might require the spack config be placed in a submodule? Ideas? - The documentation needs to be updated.
Libraries
- Mathpresso doesn't have a package, do we need it?
- VTK does have a package but it's huge, someone should strip it down.
- The support for HYPRE+cuda appears to be there in Spack develop, but I haven't tried.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.