spack.build_systems package¶
Submodules¶
spack.build_systems.aspell_dict module¶
-
class
spack.build_systems.aspell_dict.
AspellDictPackage
(spec)¶ ベースクラス:
spack.build_systems.autotools.AutotoolsPackage
Specialized class for building aspell dictionairies.
-
configure
(spec, prefix)¶ Runs configure with the arguments specified in
configure_args()
and an appropriately set prefix.
-
patch
()¶
-
view_destination
(view)¶ The target root directory: each file is added relative to this directory.
-
view_source
()¶ The source root directory that will be added to the view: files are added such that their path relative to the view destination matches their path relative to the view source.
-
spack.build_systems.autotools module¶
-
class
spack.build_systems.autotools.
AutotoolsPackage
(spec)¶ ベースクラス:
spack.package.PackageBase
Specialized class for packages built using GNU Autotools.
This class provides four phases that can be overridden:
They all have sensible defaults and for many packages the only thing necessary will be to override the helper method
configure_args()
. For a finer tuning you may also override:Method
Purpose
Specify
make
targets for the build phaseSpecify
make
targets for the install phaseRun build time tests if required
-
archive_files
¶ Files to archive for packages based on autotools
-
autoreconf
(spec, prefix)¶ Not needed usually, configure should be already there
-
autoreconf_extra_args
= []¶ Options to be passed to autoreconf when using the default implementation
-
build
(spec, prefix)¶ Makes the build targets specified by :py:attr:
~.AutotoolsPackage.build_targets
-
build_directory
¶ Override to provide another place to build the package
-
build_system_class
= 'AutotoolsPackage'¶ This attribute is used in UI queries that need to know the build system base class
-
build_time_test_callbacks
= ['check']¶ Callback names for build-time test
-
check
()¶ Searches the Makefile for targets
test
andcheck
and runs them if found.
-
configure
(spec, prefix)¶ Runs configure with the arguments specified in
configure_args()
and an appropriately set prefix.
-
configure_abs_path
¶
-
configure_args
()¶ Produces a list containing all the arguments that must be passed to configure, except
--prefix
which will be pre-pended to the list.- 戻り値
list of arguments for configure
-
configure_directory
¶ Returns the directory where 'configure' resides.
- 戻り値
directory where to find configure
-
delete_configure_to_force_update
()¶
-
enable_or_disable
(name, activation_value=None)¶ Same as
with_or_without()
but substitutewith
withenable
andwithout
withdisable
.- パラメータ
name (str) -- name of a valid multi-valued variant
activation_value (callable) --
if present accepts a single value and returns the parameter to be used leading to an entry of the type
--enable-{name}={parameter}
The special value 'prefix' can also be assigned and will return
spec[name].prefix
as activation parameter.
- 戻り値
list of arguments to configure
-
flags_to_build_system_args
(flags)¶ Produces a list of all command line arguments to pass specified compiler flags to configure.
-
force_autoreconf
= False¶ Set to true to force the autoreconf step even if configure is present
-
install
(spec, prefix)¶ Makes the install targets specified by :py:attr:
~.AutotoolsPackage.install_targets
-
install_time_test_callbacks
= ['installcheck']¶ Callback names for install-time test
-
installcheck
()¶ Searches the Makefile for an
installcheck
target and runs it if found.
-
patch_config_guess
= True¶ Whether or not to update
config.guess
on old architectures
-
phases
= ['autoreconf', 'configure', 'build', 'install']¶ Phases of a GNU Autotools package
-
set_configure_or_die
()¶ Checks the presence of a
configure
file after the autoreconf phase. If it is found sets a module attribute appropriately, otherwise raises an error.- 例外
RuntimeError -- if a configure script is not found in
configure_directory()
-
with_or_without
(name, activation_value=None)¶ Inspects a variant and returns the arguments that activate or deactivate the selected feature(s) for the configure options.
This function works on all type of variants. For bool-valued variants it will return by default
--with-{name}
or--without-{name}
. For other kinds of variants it will cycle over the allowed values and return either--with-{value}
or--without-{value}
.If activation_value is given, then for each possible value of the variant, the option
--with-{value}=activation_value(value)
or--without-{value}
will be added depending on whether or notvariant=value
is in the spec.- パラメータ
name (str) -- name of a valid multi-valued variant
activation_value (callable) --
callable that accepts a single value and returns the parameter to be used leading to an entry of the type
--with-{name}={parameter}
.The special value 'prefix' can also be assigned and will return
spec[name].prefix
as activation parameter.
- 戻り値
list of arguments to configure
-
spack.build_systems.cmake module¶
-
class
spack.build_systems.cmake.
CMakePackage
(spec)¶ ベースクラス:
spack.package.PackageBase
Specialized class for packages built using CMake
For more information on the CMake build system, see: https://cmake.org/cmake/help/latest/
This class provides three phases that can be overridden:
They all have sensible defaults and for many packages the only thing necessary will be to override
cmake_args()
. For a finer tuning you may also override:Method
Purpose
Location of the root CMakeLists.txt
Directory where to build the package
The generator used by CMake can be specified by providing the generator attribute. Per https://cmake.org/cmake/help/git-master/manual/cmake-generators.7.html, the format is: [<secondary-generator> - ]<primary_generator>. The full list of primary and secondary generators supported by CMake may be found in the documentation for the version of CMake used; however, at this time Spack supports only the primary generators "Unix Makefiles" and "Ninja." Spack's CMake support is agnostic with respect to primary generators. Spack will generate a runtime error if the generator string does not follow the prescribed format, or if the primary generator is not supported.
-
archive_files
¶ Files to archive for packages based on CMake
-
build
(spec, prefix)¶ Make the build targets
-
build_directory
¶ Returns the directory to use when building the package
- 戻り値
directory where to build the package
-
build_system_class
= 'CMakePackage'¶ This attribute is used in UI queries that need to know the build system base class
-
build_targets
= []¶
-
build_time_test_callbacks
= ['check']¶
-
check
()¶ Searches the CMake-generated Makefile for the target
test
and runs it if found.
-
cmake
(spec, prefix)¶ Runs
cmake
in the build directory
-
cmake_args
()¶ Produces a list containing all the arguments that must be passed to cmake, except:
CMAKE_INSTALL_PREFIX
CMAKE_BUILD_TYPE
which will be set automatically.
- 戻り値
list of arguments for cmake
-
flags_to_build_system_args
(flags)¶ Produces a list of all command line arguments to pass the specified compiler flags to cmake. Note CMAKE does not have a cppflags option, so cppflags will be added to cflags, cxxflags, and fflags to mimic the behavior in other tools.
-
generator
= 'Unix Makefiles'¶ The build system generator to use.
See
cmake --help
for a list of valid generators. Currently, "Unix Makefiles" and "Ninja" are the only generators that Spack supports. Defaults to "Unix Makefiles".See https://cmake.org/cmake/help/latest/manual/cmake-generators.7.html for more information.
-
install
(spec, prefix)¶ Make the install targets
-
install_targets
= ['install']¶
-
phases
= ['cmake', 'build', 'install']¶ Phases of a CMake package
-
root_cmakelists_dir
¶ The relative path to the directory containing CMakeLists.txt
This path is relative to the root of the extracted tarball, not to the
build_directory
. Defaults to the current directory.- 戻り値
directory containing CMakeLists.txt
-
std_cmake_args
¶ Standard cmake arguments provided as a property for convenience of package writers
- 戻り値
standard cmake arguments
-
spack.build_systems.cuda module¶
-
class
spack.build_systems.cuda.
CudaPackage
(spec)¶ ベースクラス:
spack.package.PackageBase
Auxiliary class which contains CUDA variant, dependencies and conflicts and is meant to unify and facilitate its usage.
-
arch_platform
= ' arch=ppc64le platform=linux'¶
-
static
cuda_flags
(arch_list)¶
-
spack.build_systems.intel module¶
-
class
spack.build_systems.intel.
IntelPackage
(spec)¶ ベースクラス:
spack.package.PackageBase
Specialized class for licensed Intel software.
This class provides two phases that can be overridden:
They both have sensible defaults and for many packages the only thing necessary will be to override setup_environment to set the appropriate environment variables.
-
blas_libs
¶
-
build_system_class
= 'IntelPackage'¶ This attribute is used in UI queries that need to know the build system base class
-
component_bin_dir
(component, **kwargs)¶
-
component_include_dir
(component, **kwargs)¶
-
component_lib_dir
(component, **kwargs)¶ Provide directory suitable for find_libraries() and SPACK_COMPILER_EXTRA_RPATHS.
-
configure
(spec, prefix)¶ Generates the silent.cfg file to pass to installer.sh.
See https://software.intel.com/en-us/articles/configuration-file-format
-
configure_rpath
()¶
-
file_to_source
¶ Full path of file to source for initializing an Intel package. A client package could override as follows: ` @property` ` def file_to_source(self):` ` return self.normalize_path("apsvars.sh", "vtune_amplifier")`
-
filter_compiler_wrappers
()¶
-
global_license_file
¶ Returns the path where a Spack-global license file should be stored.
All Intel software shares the same license, so we store it in a common 'intel' directory.
-
headers
¶
-
install
(spec, prefix)¶ Runs Intel's install.sh installation script. Afterwards, save the installer config and logs to <prefix>/.spack
-
intel64_int_suffix
¶ Provide the suffix for Intel library names to match a client application's desired int size, conveyed by the active spec variant. The possible suffixes and their meanings are:
ilp64
all of int, long, and pointer are 64 bit, `` lp64`` only long and pointer are 64 bit; int will be 32bit.
-
lapack_libs
¶
-
libs
¶
-
license_comment
= '#'¶ Comment symbol used in the license.lic file
-
license_files
¶ Built-in mutable sequence.
If no argument is given, the constructor creates a new empty list. The argument must be an iterable if specified.
-
license_required
¶ bool(x) -> bool
Returns True when the argument x is true, False otherwise. The builtins True and False are the only two instances of the class bool. The class bool is a subclass of the class int, and cannot be subclassed.
-
license_url
= 'https://software.intel.com/en-us/articles/intel-license-manager-faq'¶ URL providing information on how to acquire a license key
-
license_vars
= ['INTEL_LICENSE_FILE']¶ Environment variables that Intel searches for a license file
-
mpi_compiler_wrappers
¶ Return paths to compiler wrappers as a dict of env-like names
-
mpi_setup_dependent_environment
(spack_env, run_env, dependent_spec, compilers_of_client={})¶ Unified back-end for setup_dependent_environment() of Intel packages that provide 'mpi'.
- パラメータ
run_env, dependent_spec (spack_env,) -- same as in setup_dependent_environment().
compilers_of_client (dict) -- Conveys spack_cc, spack_cxx, etc., from the scope of dependent packages; constructed in caller.
-
normalize_path
(component_path, component_suite_dir=None, relative=False)¶ Returns the absolute or relative path to a component or file under a component suite directory.
Intel's product names, scope, and directory layout changed over the years. This function provides a unified interface to their directory names.
- パラメータ
component_path (str) -- a component name like 'mkl', or 'mpi', or a deeper relative path.
component_suite_dir (str) --
_Unversioned_ name of the expected parent directory of component_path. When absent or None, an appropriate default will be used. A present but empty string "" requests that component_path refer to self.prefix directly.
Typical values: compilers_and_libraries, composer_xe, parallel_studio_xe.
Also supported: advisor, inspector, vtune. The actual directory name for these suites varies by release year. The name will be corrected as needed for use in the return value.
relative (bool) -- When True, return path relative to self.prefix, otherwise, return an absolute path (the default).
-
normalize_suite_dir
(suite_dir_name, version_globs=['*.*.*'])¶ Returns the version-specific and absolute path to the directory of an Intel product or a suite of product components.
- パラメータ
suite_dir_name (str) --
Name of the product directory, without numeric version.
Examples:
composer_xe, parallel_studio_xe, compilers_and_libraries
The following will work as well, even though they are not directly targets for Spack installation:
advisor_xe, inspector_xe, vtune_amplifier_xe, performance_snapshots (new name for vtune as of 2018)
These are single-component products without subordinate components and are normally made available to users by a toplevel psxevars.sh or equivalent file to source (and thus by the modulefiles that Spack produces).
version_globs (list of str) -- Suffix glob patterns (most specific first) expected to qualify suite_dir_name to its fully version-specific install directory (as opposed to a compatibility directory or symlink).
-
openmp_libs
¶ Supply LibraryList for linking OpenMP
-
phases
= ['configure', 'install']¶ Phases of an Intel package
-
pset_components
¶
-
scalapack_libs
¶
-
setup_dependent_environment
(spack_env, run_env, dependent_spec)¶ Set up the environment of packages that depend on this one.
This is similar to
setup_environment
, but it is used to modify the compile and runtime environments of packages that depend on this one. This gives packages like Python and others that follow the extension model a way to implement common environment or compile-time settings for dependencies.This is useful if there are some common steps to installing all extensions for a certain package.
Example:
Installing python modules generally requires
PYTHONPATH
to point to thelib/pythonX.Y/site-packages
directory in the module's install prefix. This method could be used to set that variable.
- パラメータ
spack_env (EnvironmentModifications) -- List of environment modifications to be applied when the dependent package is built within Spack.
run_env (EnvironmentModifications) -- List of environment modifications to be applied when the dependent package is run outside of Spack. These are added to the resulting module file.
dependent_spec (Spec) -- The spec of the dependent package about to be built. This allows the extendee (self) to query the dependent's state. Note that this package's spec is available as
self.spec
.
-
setup_dependent_package
(module, dep_spec)¶ Set up Python module-scope variables for dependent packages.
Called before the install() method of dependents.
Default implementation does nothing, but this can be overridden by an extendable package to set up the module of its extensions. This is useful if there are some common steps to installing all extensions for a certain package.
Examples:
Extensions often need to invoke the
python
interpreter from the Python installation being extended. This routine can put apython()
Executable object in the module scope for the extension package to simplify extension installs.MPI compilers could set some variables in the dependent's scope that point to
mpicc
,mpicxx
, etc., allowing them to be called by common name regardless of which MPI is used.BLAS/LAPACK implementations can set some variables indicating the path to their libraries, since these paths differ by BLAS/LAPACK implementation.
- パラメータ
module (spack.package.PackageBase.module) -- The Python
module
object of the dependent package. Packages can use this to set module-scope variables for the dependent to use.dependent_spec (Spec) -- The spec of the dependent package about to be built. This allows the extendee (self) to query the dependent's state. Note that this package's spec is available as
self.spec
.
-
setup_environment
(spack_env, run_env)¶ Adds environment variables to the generated module file.
These environment variables come from running:
$ source parallel_studio_xe_2017/bin/psxevars.sh intel64 [and likewise for MKL, MPI, and other components]
-
tbb_headers
¶
-
tbb_libs
¶ Supply LibraryList for linking TBB
-
uninstall_ism
()¶
-
version_yearlike
¶ Return the version in a unified style, suitable for Version class conditionals.
-
version_years
= {'intel-ipp@9.0:9.99': 2016, 'intel-mkl@11.3.0:11.3.999': 2016, 'intel-mpi@5.1:5.99': 2016}¶
-
-
spack.build_systems.intel.
debug_print
(msg, *args)¶ Prints a message (usu. a variable) and the callers' names for a couple of stack frames.
-
spack.build_systems.intel.
raise_lib_error
(*args)¶ Bails out with an error message. Shows args after the first as one per line, tab-indented, useful for long paths to line up and stand out.
spack.build_systems.makefile module¶
-
class
spack.build_systems.makefile.
MakefilePackage
(spec)¶ ベースクラス:
spack.package.PackageBase
Specialized class for packages that are built using editable Makefiles
This class provides three phases that can be overridden:
It is usually necessary to override the
edit()
phase, whilebuild()
andinstall()
have sensible defaults. For a finer tuning you may override:Method
Purpose
Specify
make
targets for the build phaseSpecify
make
targets for the install phaseDirectory where the Makefile is located
-
build
(spec, prefix)¶ Calls make, passing
build_targets
as targets.
-
build_directory
¶ Returns the directory containing the main Makefile
- 戻り値
build directory
-
build_system_class
= 'MakefilePackage'¶ This attribute is used in UI queries that need to know the build system base class
-
build_time_test_callbacks
= ['check']¶ Callback names for build-time test
-
check
()¶ Searches the Makefile for targets
test
andcheck
and runs them if found.
-
edit
(spec, prefix)¶ Edits the Makefile before calling make. This phase cannot be defaulted.
-
install
(spec, prefix)¶ Calls make, passing
install_targets
as targets.
-
install_time_test_callbacks
= ['installcheck']¶ Callback names for install-time test
-
installcheck
()¶ Searches the Makefile for an
installcheck
target and runs it if found.
-
phases
= ['edit', 'build', 'install']¶ Phases of a package that is built with an hand-written Makefile
-
spack.build_systems.meson module¶
-
class
spack.build_systems.meson.
MesonPackage
(spec)¶ ベースクラス:
spack.package.PackageBase
Specialized class for packages built using Meson
For more information on the Meson build system, see: https://mesonbuild.com/
This class provides three phases that can be overridden:
They all have sensible defaults and for many packages the only thing necessary will be to override
meson_args()
. For a finer tuning you may also override:Method
Purpose
Location of the root MesonLists.txt
Directory where to build the package
-
archive_files
¶ Files to archive for packages based on Meson
-
build
(spec, prefix)¶ Make the build targets
-
build_directory
¶ Returns the directory to use when building the package
- 戻り値
directory where to build the package
-
build_system_class
= 'MesonPackage'¶ This attribute is used in UI queries that need to know the build system base class
-
build_targets
= []¶
-
build_time_test_callbacks
= ['check']¶
-
check
()¶ Searches the Meson-generated file for the target
test
and runs it if found.
-
flags_to_build_system_args
(flags)¶ Produces a list of all command line arguments to pass the specified compiler flags to meson.
-
install
(spec, prefix)¶ Make the install targets
-
install_targets
= ['install']¶
-
meson
(spec, prefix)¶ Runs
meson
in the build directory
-
meson_args
()¶ Produces a list containing all the arguments that must be passed to meson, except:
--prefix
--libdir
--buildtype
--strip
which will be set automatically.
- 戻り値
list of arguments for meson
-
phases
= ['meson', 'build', 'install']¶ Phases of a Meson package
-
root_mesonlists_dir
¶ The relative path to the directory containing meson.build
This path is relative to the root of the extracted tarball, not to the
build_directory
. Defaults to the current directory.- 戻り値
directory containing meson.build
-
std_meson_args
¶ Standard meson arguments provided as a property for convenience of package writers
- 戻り値
standard meson arguments
-
spack.build_systems.octave module¶
-
class
spack.build_systems.octave.
OctavePackage
(spec)¶ ベースクラス:
spack.package.PackageBase
Specialized class for Octave packages. See https://www.gnu.org/software/octave/doc/v4.2.0/Installing-and-Removing-Packages.html for more information.
This class provides the following phases that can be overridden:
-
build_system_class
= 'OctavePackage'¶
-
install
(spec, prefix)¶ Install the package from the archive file
-
phases
= ['install']¶
-
setup_environment
(spack_env, run_env)¶ Set up the compile and runtime environments for a package.
-
spack.build_systems.perl module¶
-
class
spack.build_systems.perl.
PerlPackage
(spec)¶ ベースクラス:
spack.package.PackageBase
Specialized class for packages that are built using Perl.
This class provides four phases that can be overridden if required:
- The default methods use, in order of preference:
Makefile.PL,
Build.PL.
Some packages may need to override
configure_args()
, which produces a list of arguments forconfigure()
. Arguments should not include the installation base directory.-
build
(spec, prefix)¶ Builds a Perl package.
-
build_system_class
= 'PerlPackage'¶ This attribute is used in UI queries that need to know the build system base class
-
build_time_test_callbacks
= ['check']¶ Callback names for build-time test
-
check
()¶ Runs built-in tests of a Perl package.
-
configure
(spec, prefix)¶ Runs Makefile.PL or Build.PL with arguments consisting of an appropriate installation base directory followed by the list returned by
configure_args()
.- 例外
RuntimeError -- if neither Makefile.PL or Build.PL exist
-
configure_args
()¶ Produces a list containing the arguments that must be passed to
configure()
. Arguments should not include the installation base directory, which is prepended automatically.- 戻り値
list of arguments for Makefile.PL or Build.PL
-
install
(spec, prefix)¶ Installs a Perl package.
-
phases
= ['configure', 'build', 'install']¶ Phases of a Perl package
spack.build_systems.python module¶
-
class
spack.build_systems.python.
PythonPackage
(spec)¶ ベースクラス:
spack.package.PackageBase
Specialized class for packages that are built using Python setup.py files
This class provides the following phases that can be overridden:
build
build_py
build_ext
build_clib
build_scripts
clean
install
install_lib
install_headers
install_scripts
install_data
sdist
register
bdist
bdist_dumb
bdist_rpm
bdist_wininst
upload
check
These are all standard setup.py commands and can be found by running:
$ python setup.py --help-commands
By default, only the 'build' and 'install' phases are run, but if you need to run more phases, simply modify your
phases
list like so:phases = ['build_ext', 'install', 'bdist']
Each phase provides a function <phase> that runs:
$ python -s setup.py --no-user-cfg <phase>
Each phase also has a <phase_args> function that can pass arguments to this call. All of these functions are empty except for the
install_args
function, which passes--prefix=/path/to/installation/directory
.If you need to run a phase which is not a standard setup.py command, you'll need to define a function for it like so:
def configure(self, spec, prefix): self.setup_py('configure')
-
add_files_to_view
(view, merge_map)¶ Given a map of package files to destination paths in the view, add the files to the view. By default this adds all files. Alternative implementations may skip some files, for example if other packages linked into the view already include the file.
-
bdist
(spec, prefix)¶ Create a built (binary) distribution.
-
bdist_args
(spec, prefix)¶ Arguments to pass to bdist.
-
bdist_dumb
(spec, prefix)¶ Create a "dumb" built distribution.
-
bdist_dumb_args
(spec, prefix)¶ Arguments to pass to bdist_dumb.
-
bdist_rpm
(spec, prefix)¶ Create an RPM distribution.
-
bdist_rpm_args
(spec, prefix)¶ Arguments to pass to bdist_rpm.
-
bdist_wininst
(spec, prefix)¶ Create an executable installer for MS Windows.
-
bdist_wininst_args
(spec, prefix)¶ Arguments to pass to bdist_wininst.
-
build
(spec, prefix)¶ Build everything needed to install.
-
build_args
(spec, prefix)¶ Arguments to pass to build.
-
build_clib
(spec, prefix)¶ Build C/C++ libraries used by Python extensions.
-
build_clib_args
(spec, prefix)¶ Arguments to pass to build_clib.
-
build_directory
¶ The directory containing the
setup.py
file.
-
build_ext
(spec, prefix)¶ Build C/C++ extensions (compile/link to build directory).
-
build_ext_args
(spec, prefix)¶ Arguments to pass to build_ext.
-
build_py
(spec, prefix)¶ "Build" pure Python modules (copy to build directory).
-
build_py_args
(spec, prefix)¶ Arguments to pass to build_py.
-
build_scripts
(spec, prefix)¶ "Build" scripts (copy and fixup #! line).
-
build_system_class
= 'PythonPackage'¶
-
build_time_test_callbacks
= ['test']¶ Callback names for build-time test
-
check
(spec, prefix)¶ Perform some checks on the package.
-
check_args
(spec, prefix)¶ Arguments to pass to check.
-
clean
(spec, prefix)¶ Clean up temporary files from 'build' command.
-
clean_args
(spec, prefix)¶ Arguments to pass to clean.
-
import_module_test
()¶ Attempts to import the module that was just installed.
This test is only run if the package overrides
import_modules
with a list of module names.
-
import_modules
= []¶
-
install
(spec, prefix)¶ Install everything from build directory.
-
install_args
(spec, prefix)¶ Arguments to pass to install.
-
install_data
(spec, prefix)¶ Install data files.
-
install_data_args
(spec, prefix)¶ Arguments to pass to install_data.
-
install_headers
(spec, prefix)¶ Install C/C++ header files.
-
install_headers_args
(spec, prefix)¶ Arguments to pass to install_headers.
-
install_lib
(spec, prefix)¶ Install all Python modules (extensions and pure Python).
-
install_lib_args
(spec, prefix)¶ Arguments to pass to install_lib.
-
install_scripts
(spec, prefix)¶ Install scripts (Python or otherwise).
-
install_scripts_args
(spec, prefix)¶ Arguments to pass to install_scripts.
-
install_time_test_callbacks
= ['import_module_test']¶ Callback names for install-time test
-
phases
= ['build', 'install']¶
-
py_namespace
= None¶
-
python
(*args, **kwargs)¶
-
register
(spec, prefix)¶ Register the distribution with the Python package index.
-
register_args
(spec, prefix)¶ Arguments to pass to register.
-
remove_files_from_view
(view, merge_map)¶ Given a map of package files to files currently linked in the view, remove the files from the view. The default implementation removes all files. Alternative implementations may not remove all files. For example if two packages include the same file, it should only be removed when both packages are removed.
-
sdist
(spec, prefix)¶ Create a source distribution (tarball, zip file, etc.).
-
sdist_args
(spec, prefix)¶ Arguments to pass to sdist.
-
setup_file
()¶ Returns the name of the setup file to use.
-
setup_py
(*args, **kwargs)¶
-
test
()¶ Run unit tests after in-place build.
These tests are only run if the package actually has a 'test' command.
-
test_args
(spec, prefix)¶ Arguments to pass to test.
-
upload
(spec, prefix)¶ Upload binary package to PyPI.
-
upload_args
(spec, prefix)¶ Arguments to pass to upload.
-
view_file_conflicts
(view, merge_map)¶ Report all file conflicts, excepting special cases for python. Specifically, this does not report errors for duplicate __init__.py files for packages in the same namespace.
spack.build_systems.qmake module¶
-
class
spack.build_systems.qmake.
QMakePackage
(spec)¶ ベースクラス:
spack.package.PackageBase
Specialized class for packages built using qmake.
For more information on the qmake build system, see: http://doc.qt.io/qt-5/qmake-manual.html
This class provides three phases that can be overridden:
They all have sensible defaults and for many packages the only thing necessary will be to override
qmake_args()
.-
build
(spec, prefix)¶ Make the build targets
-
build_system_class
= 'QMakePackage'¶ This attribute is used in UI queries that need to know the build system base class
-
build_time_test_callbacks
= ['check']¶ Callback names for build-time test
-
check
()¶ Searches the Makefile for a
check:
target and runs it if found.
-
install
(spec, prefix)¶ Make the install targets
-
phases
= ['qmake', 'build', 'install']¶ Phases of a qmake package
-
qmake
(spec, prefix)¶ Run
qmake
to configure the project and generate a Makefile.
-
qmake_args
()¶ Produces a list containing all the arguments that must be passed to qmake
-
spack.build_systems.r module¶
-
class
spack.build_systems.r.
RPackage
(spec)¶ ベースクラス:
spack.package.PackageBase
Specialized class for packages that are built using R.
For more information on the R build system, see: https://stat.ethz.ch/R-manual/R-devel/library/utils/html/INSTALL.html
This class provides a single phase that can be overridden:
It has sensible defaults, and for many packages the only thing necessary will be to add dependencies
-
build_system_class
= 'RPackage'¶ This attribute is used in UI queries that need to know the build system base class
-
configure_args
()¶ Arguments to pass to install via
--configure-args
.
-
configure_vars
()¶ Arguments to pass to install via
--configure-vars
.
-
install
(spec, prefix)¶ Installs an R package.
-
phases
= ['install']¶
-
spack.build_systems.scons module¶
-
class
spack.build_systems.scons.
SConsPackage
(spec)¶ ベースクラス:
spack.package.PackageBase
Specialized class for packages built using SCons.
See http://scons.org/documentation.html for more information.
This class provides the following phases that can be overridden:
Packages that use SCons as a build system are less uniform than packages that use other build systems. Developers can add custom subcommands or variables that control the build. You will likely need to override
build_args()
to pass the appropriate variables.-
build
(spec, prefix)¶ Build the package.
-
build_args
(spec, prefix)¶ Arguments to pass to build.
-
build_system_class
= 'SConsPackage'¶ To be used in UI queries that require to know which build-system class we are using
-
build_time_test_callbacks
= ['test']¶ Callback names for build-time test
-
install
(spec, prefix)¶ Install the package.
-
install_args
(spec, prefix)¶ Arguments to pass to install.
-
phases
= ['build', 'install']¶ Phases of a SCons package
-
test
()¶ Run unit tests after build.
By default, does nothing. Override this if you want to add package-specific tests.
-
spack.build_systems.waf module¶
-
class
spack.build_systems.waf.
WafPackage
(spec)¶ ベースクラス:
spack.package.PackageBase
Specialized class for packages that are built using the Waf build system. See https://waf.io/book/ for more information.
This class provides the following phases that can be overridden:
configure
build
install
These are all standard Waf commands and can be found by running:
$ python waf --help
Each phase provides a function <phase> that runs:
$ python waf -j<jobs> <phase>
where <jobs> is the number of parallel jobs to build with. Each phase also has a <phase_args> function that can pass arguments to this call. All of these functions are empty except for the
configure_args
function, which passes--prefix=/path/to/installation/prefix
.-
build
(spec, prefix)¶ Executes the build.
-
build_args
()¶ Arguments to pass to build.
-
build_directory
¶ The directory containing the
waf
file.
-
build_system_class
= 'WafPackage'¶
-
build_time_test_callbacks
= ['test']¶
-
configure
(spec, prefix)¶ Configures the project.
-
configure_args
()¶ Arguments to pass to configure.
-
install
(spec, prefix)¶ Installs the targets on the system.
-
install_args
()¶ Arguments to pass to install.
-
install_time_test_callbacks
= ['installtest']¶
-
installtest
()¶ Run unit tests after install.
By default, does nothing. Override this if you want to add package-specific tests.
-
phases
= ['configure', 'build', 'install']¶
-
python
(*args, **kwargs)¶ The python
Executable
.
-
test
()¶ Run unit tests after build.
By default, does nothing. Override this if you want to add package-specific tests.
-
waf
(*args, **kwargs)¶ Runs the waf
Executable
.