Telcon: 2019 02 28
Peter Scheibel edited this page Feb 28, 2019
·
11 revisions
- Peter Scheibel (host)
- Daniel Topa
- Patrick Gartung
- Greg Becker
- David N.
- Recently-merged PRs
- (Adam J. Stewart) Fix Make test on systems using languages other than English: https://github.com/spack/spack/pull/10499
- (Phil Carns) Allow running
setup-env.sh
in a script: https://github.com/spack/spack/pull/9712 - (Massimiliano Culpo) Allow packages to customize include directories: https://github.com/spack/spack/pull/10623
- (Chris Green) Allow secondary CMake generators: https://github.com/spack/spack/pull/9324
- (Adam J. Stewart) All Python dependencies are now optional: https://github.com/spack/spack/pull/10335
- Default options generally install same dependencies as before
- Depending on use case, you may be able to deactivate some dependencies
- Greg Becker: what defaults to use when automatically building compilers
- If you build foo %gcc and you don't have gcc on your system, should Spack install it?
- Should it do this by default?
- Perhaps not: installing compilers is expensive
- Default=true would be good for environments: where you want to install some compilers and then build a bunch of packages with those compilers. Environments could be modified to bootstrap the compiler setup, but auto-installing the compilers would be useful.
- Dan Topa:
spack compiler find
should add a module to the compilers.yaml config