summaryrefslogtreecommitdiff
path: root/lib
diff options
context:
space:
mode:
authorChuck Atkins <chuck.atkins@kitware.com>2019-05-02 16:21:06 -0400
committerOmar Padron <omar.padron@kitware.com>2019-05-02 16:21:06 -0400
commitf44443ed3a2b99a6a17a6c8d230be886842ae90e (patch)
tree108f125a51e1aeb1f463a71e9fcf926221581a05 /lib
parent5b82bf47af78a95ff38d0abc4e24255962914639 (diff)
downloadspack-f44443ed3a2b99a6a17a6c8d230be886842ae90e.tar.gz
spack-f44443ed3a2b99a6a17a6c8d230be886842ae90e.tar.bz2
spack-f44443ed3a2b99a6a17a6c8d230be886842ae90e.tar.xz
spack-f44443ed3a2b99a6a17a6c8d230be886842ae90e.zip
llvm: depend on python only when +python (#11348)
Based on the LLVM documentation [1], Python is used to run the automated test suite. Therefore is it always a dependency for LLVM. However, if build without Python (~python), we limit it to a build time dependency. Note that py-lit is not added as a spack dependency even though it is available as a spack package. This is because it is already included in llvm and llvm is difficult to configure using an external py-lit (several CMake variables to set correctly). Additionally, having py-lit as a spack dependency adds Python as a runtime dependency for llvm even though it is not required at runtime. [1] https://llvm.org/docs/GettingStarted.html#requirements
Diffstat (limited to 'lib')
0 files changed, 0 insertions, 0 deletions