1b3f546ba4
* add support for static (via ~shared) and use vtk-m 1.2 * updating vtkh package to output cmake configure file and pinning it to vtkm 1.2 * trying a different cmake for vtkh * removing problematic b * making conduit respect ~python * fixing ascent python logic * update ascent package * consistant cmake usage * conditionally add tbb in ascent if vtkh * applying becker fix * adding vtkh tag * fixing vtkh tagged version * updating ascent and conduit for static builds * enabling openmp * reverting files that should not have been changed * ascent updates * more robust handling of variants * fixing ascent package typo * ascent: add optional support for mfem * enable mfem conduit support for ascent * add optional adios dep to conduit * remove ver req from conduit * ascent: remove confusing comment * tweaks to conduit and ascent pkg recipes * fix typo in conduit package * pref conduit master * fixing mfem typo for ascent * reverting files * adding mirror for bzip * changing mfem to depend on conduit@master to get updated relay * restore use of conduit 0.3.1 or greater for mfem * set master as prefered conduit version * allow mfem to use conduit master * adding rover package and editing ascent * updating vtkm cmake dep * updates from axom * guard ascent python support on +shared * removing rover to simply ascent package * add fortran variant to conduit, to allow us to turn off conduit support even when a fortran compiler is specified * fix fortran compiler check so it can work on cray systems * working towards cuda fix for vtkm lagrange filter * update ascent package with more variants, and patch to avoid nvcc issue * hdf5 flags fix for BGQ * flake8 * extra guards for cuda patch * conduit and ascent fortran fix * fix patch for non cuda case * add test variant to conduit, tweak ascent pkg * change min ver of cmake used for ascent * h5z-zfp package: unset FC when ~fortran * conform to expected upstream solution * pinning vtkm * going back to vtkm master * add back vtk-m variant for shared libs * update ascent and vtkh packages * wire up option to run tests during install * add post install test * add testing to ascent * tweak for blueos xl * add ctest output on error for run_tests * enable ctest output on error for run_tests * add testing of the using-with-make example * update using-with-make examples * typo in ascent using-with-cmake test * fix ascent using test exe names * more fixes, less sleep * more fixes, less sleep ... * remove unwired up version * improvments suggested on review * adding new cmake * Update package.py * Update package.py * changes post cori os update * fix cray hack * Update package.py Fixing 'fix'. Inconsistent variable names in conduit package * type in spack recipes * add zfp support to conduit * fix indent error in conduit pkg * move to use build phases, add sphinx rtd as dep, fix ex names in tests * add conduit 0.5.0 release * flake8 * remove old cray hack * incorp feedback from review * fix to use proper build env sig |
||
|---|---|---|
| .github | ||
| bin | ||
| etc/spack/defaults | ||
| lib/spack | ||
| share/spack | ||
| var/spack | ||
| .codecov.yml | ||
| .coveragerc | ||
| .dockerignore | ||
| .flake8 | ||
| .flake8_packages | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .mailmap | ||
| .readthedocs.yml | ||
| .travis.yml | ||
| CHANGELOG.md | ||
| COPYRIGHT | ||
| LICENSE-APACHE | ||
| LICENSE-MIT | ||
| NOTICE | ||
| README.md | ||
Spack
Spack is a multi-platform package manager that builds and installs multiple versions and configurations of software. It works on Linux, macOS, and many supercomputers. Spack is non-destructive: installing a new version of a package does not break existing installations, so many configurations of the same package can coexist.
Spack offers a simple "spec" syntax that allows users to specify versions and configuration options. Package files are written in pure Python, and specs allow package authors to write a single script for many different builds of the same package. With Spack, you can build your software all the ways you want to.
See the Feature Overview for examples and highlights.
To install spack and your first package, make sure you have Python. Then:
$ git clone https://github.com/spack/spack.git
$ cd spack/bin
$ ./spack install zlib
Documentation
Full documentation is available, or
run spack help or spack help --all.
Tutorial
We maintain a hands-on tutorial. It covers basic to advanced usage, packaging, developer features, and large HPC deployments. You can do all of the exercises on your own laptop using a Docker container.
Feel free to use these materials to teach users at your organization about Spack.
Community
Spack is an open source project. Questions, discussion, and contributions are welcome. Contributions can be anything from new packages to bugfixes, documentation, or even new core features.
Resources:
- Slack workspace: spackpm.slack.com. To get an invitation, click here.
- Mailing list: groups.google.com/d/forum/spack
- Twitter: @spackpm. Be sure to
@mentionus!
Contributing
Contributing to Spack is relatively easy. Just send us a
pull request.
When you send your request, make develop the destination branch on the
Spack repository.
Your PR must pass Spack's unit tests and documentation tests, and must be PEP 8 compliant. We enforce these guidelines with Travis CI. To run these tests locally, and for helpful tips on git, see our Contribution Guide.
Spack uses a rough approximation of the
Git Flow
branching model. The develop branch contains the latest
contributions, and master is always tagged and points to the latest
stable release.
Code of Conduct
Please note that Spack has a Code of Conduct. By participating in the Spack community, you agree to abide by its rules.
Authors
Many thanks go to Spack's contributors.
Spack was created by Todd Gamblin, tgamblin@llnl.gov.
Citing Spack
If you are referencing Spack in a publication, please cite the following paper:
- Todd Gamblin, Matthew P. LeGendre, Michael R. Collette, Gregory L. Lee, Adam Moody, Bronis R. de Supinski, and W. Scott Futral. The Spack Package Manager: Bringing Order to HPC Software Chaos. In Supercomputing 2015 (SC’15), Austin, Texas, November 15-20 2015. LLNL-CONF-669890.
License
Spack is distributed under the terms of both the MIT license and the Apache License (Version 2.0). Users may choose either license, at their option.
All new contributions must be made under both the MIT and Apache-2.0 licenses.
See LICENSE-MIT, LICENSE-APACHE, COPYRIGHT, and NOTICE for details.
SPDX-License-Identifier: (Apache-2.0 OR MIT)
LLNL-CODE-647188