summaryrefslogtreecommitdiff
path: root/.flake8_packages
diff options
context:
space:
mode:
authorbecker33 <becker33@llnl.gov>2017-12-20 15:40:38 -0800
committerTodd Gamblin <tgamblin@llnl.gov>2018-01-19 09:32:24 -0800
commite0826804c21cb35052bc89eda635e1fa69d71e93 (patch)
tree7b31749cb47ba25210703f2a80fc1b19d0dd219b /.flake8_packages
parentc2a10a2aa23f3905ee22bb4b7c79ab963d966a9d (diff)
downloadspack-e0826804c21cb35052bc89eda635e1fa69d71e93.tar.gz
spack-e0826804c21cb35052bc89eda635e1fa69d71e93.tar.bz2
spack-e0826804c21cb35052bc89eda635e1fa69d71e93.tar.xz
spack-e0826804c21cb35052bc89eda635e1fa69d71e93.zip
Compiler flag handlers (#6415)
This adds the ability for packages to apply compiler flags in one of three ways: by injecting them into the compiler wrapper calls (the default in this PR and previously the only automated choice); exporting environment variable definitions for variables with corresponding names (e.g. CPPFLAGS=...); providing them as arguments to the build system (e.g. configure). When applying compiler flags using build system arguments, a package must implement the 'flags_to_build_system_args" function. This is provided for CMake and autotools packages, so for packages which subclass those build systems, they need only update their flag handler method specify which compiler flags should be specified as arguments to the build system. Convenience methods are provided to specify that all flags be applied in one of the 3 available ways, so a custom implementation is only required if more than one method of applying compiler flags is needed. This also removes redundant build system definitions from tutorial examples
Diffstat (limited to '.flake8_packages')
0 files changed, 0 insertions, 0 deletions