diff options
author | becker33 <becker33@llnl.gov> | 2017-12-20 15:40:38 -0800 |
---|---|---|
committer | scheibelp <scheibel1@llnl.gov> | 2017-12-20 15:40:38 -0800 |
commit | 28d8784ab9162118800f0fd1c5ee7da279ecbf83 (patch) | |
tree | e923ccf164fabc0437231ff88b7d2e37a225f6d0 /CONTRIBUTING.md | |
parent | ef2e51571d792f25595b0b28887c38e41057dd71 (diff) | |
download | spack-28d8784ab9162118800f0fd1c5ee7da279ecbf83.tar.gz spack-28d8784ab9162118800f0fd1c5ee7da279ecbf83.tar.bz2 spack-28d8784ab9162118800f0fd1c5ee7da279ecbf83.tar.xz spack-28d8784ab9162118800f0fd1c5ee7da279ecbf83.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 'CONTRIBUTING.md')
0 files changed, 0 insertions, 0 deletions