zhangyiss/spack
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
A flexible package manager that supports multiple versions, configurations, platforms, and compilers.
8,091 Commits 246 Branches 186 Tags 666 MiB
Python 97.3%
Shell 2.1%
C 0.2%
322b016230
Go to file
Kelly (KT) Thompson 322b016230 Provide build_type variant for Metis. (#6808) 
* Provide build_type variant for Metis.

+ Ideally, we would make Metis a CMakePackage, but `metis@:5` doesn't use CMake.
+ For now, provide a `build_type=` variant similar what is found in
  CMakePackage.
+ There is a potential for duplicate specification of `CMAKE_BUILD_TYPE` if both
  variants `+debug` and `build_type=` are specified. I am looking for advice on
  how this can be resolved.

* Update metis recipe in response to flake8 and user comments.

+ Wrap comment lines that used more than 80 columns.
+ Change `+debug` variant to avoid potential for multiple `-DCMAKE_BUID_TYPE=`
  arguments provided to cmake.  Specifying this variant no longer appends this
  configure option.  However, if `+debug` is specified, require
  `build_type=Debug` to maintain expected behavior.

* For metis, remove +debug variant; use build_type= instead.

+ Update recipe for metis@4 to extract `build_type=` values and set `OPTFLAGS`
  accordingly.
+ For metis@5:, the behavior from the previously supported variant `+debug` can
  be obtained with the options `+gdb build_type=Debug`

* Conflicts added for metis@4 when build_type != Release|Debug.

* Use spack function conflicts instead of 'raise InstallError'.
2018-01-05 13:45:21 -06:00
bin Replace github.com/llnl/spack with github.com/spack/spack (#6142) 2017-11-04 17:08:04 -07:00
etc/spack/defaults Introduce virtual dependency pkgconfig (#5198) 2017-11-23 08:05:38 -07:00
lib/spack Fix HTML detection (#6394) 2018-01-02 21:21:36 -06:00
share/spack Reduce the calls to the python interpreter during initialization (#6312) 2017-11-15 17:38:40 -07:00
templates/modules Replace github.com/llnl/spack with github.com/spack/spack (#6142) 2017-11-04 17:08:04 -07:00
var/spack Provide build_type variant for Metis. (#6808) 2018-01-05 13:45:21 -06:00
.codecov.yml
.coveragerc
.flake8
.flake8_packages
.gitignore Ignore log files that appear in root dir with "spack -d install ..." (#6670) 2017-12-13 08:35:39 +01:00
.mailmap Update for 'eccodes'. (#6604) 2017-12-08 09:34:37 +01:00
.travis.yml travis: removed /usr/local/include/c++ before installing gcc on OSX (#6515) 2017-11-29 11:33:00 -08:00
CODE_OF_CONDUCT.md Add a code of conduct to Spack (#6251) 2017-11-09 21:18:58 -08:00
CONTRIBUTING.md Add basic CONTRIBUTING.md that points to contribution guide docs (#6203) 2017-11-08 11:09:11 -08:00
issue_template.md Added an issue template for Github (#6205) 2017-11-13 10:51:53 -07:00
LICENSE
NOTICE
pytest.ini
README.md add artisanal handcrafted SVG Spack logo. (#6165) 2017-11-06 22:42:16 -08:00

README.md

Spack Spack

Build Status codecov Read the Docs Slack

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 libelf

Documentation

Full documentation for Spack is the first place to look.

Try the Spack Tutorial, to learn how to use spack, write packages, or deploy packages for users at your site.

See also:

Get Involved!

Spack is an open source project. Questions, discussion, and contributions are welcome. Contributions can be anything from new packages to bugfixes, or even new core features.

Mailing list

If you are interested in contributing to spack, join the mailing list. We're using Google Groups for this:

Slack channel

Spack has a Slack channel where you can chat about all things Spack:

Sign up here to get an invitation mailed to you.

Contributions

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.

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:

Release

Spack is released under an LGPL license. For more details see the NOTICE and LICENSE files.

LLNL-CODE-647188

Analytics