Is Spack able to include a package with mainly script files and a particular workflow for running? #20521
-
Hi, We have put our library Z-checker in Spack: Z-checker is a data compression assessment library including many useful analysis implementations. As for users, however, in order to the compression assessment, they often also need to install compressors or they can also use their own compressors in the z-checker assessment. Simply installing those dependent compressor packages doesn't work because linking them together also requires some specific scripts and operations. So, we developed Z-checker-installer to compile some individual code files with 'main function' using particular custom Makefiles and do a set of configurations (e.g., copy some scripts to some directories) particularly, so as to link the compressors with Z-checker. That is, Z-checker-instlaller is rather like an execution environment controller to aggregate multiple libraries/analysis/scripts together. For the installation, the user just needs to run z-checker-installer.sh to install everything for the assessment environment. My question is: Thanks. Reference: Sheng |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Yes, you can put z-checker into Spack. The package.py file in Spack can be specialized to particular build systems, but the basic
that method will install the package into the prefix, parameterized by For example, if there were one variant
|
Beta Was this translation helpful? Give feedback.
Yes, you can put z-checker into Spack.
The package.py file in Spack can be specialized to particular build systems, but the basic
Package
type is always an option. If your package inherits from Package, you can simply define aninstall
method with the following signature.that method will install the package into the prefix, parameterized by
spec
.For example, if there were one variant
bar
on packagefoo
, you may have an install method that looks something like