... | ... | @@ -61,6 +61,7 @@ The user configuration file is queried first and can be used to overwrite the de |
|
|
Format:
|
|
|
----
|
|
|
---
|
|
|
overlays:
|
|
|
name_of_overlay:
|
|
|
root_dir: <DIR>
|
|
|
modulefiles_root_dir: <DIR>
|
... | ... | @@ -115,11 +116,13 @@ With the implementation of overlays a new format for the so called variant files |
|
|
==== YAML format of variant files
|
|
|
----
|
|
|
---
|
|
|
defaults:
|
|
|
overlay: <overlay-name>
|
|
|
module_name/module_version:
|
|
|
variants:
|
|
|
- relstage: <release-stage>
|
|
|
modulefiles_root_dir: <modulefile-root-dir>
|
|
|
use_flags: <flags>
|
|
|
overlay: <overlay-name>
|
|
|
dependencies:
|
|
|
- dependency_1
|
|
|
- dependency_2
|
... | ... | @@ -141,3 +144,6 @@ module_name/module_version: |
|
|
* `b:` build-dependency: A build-dependency is required at build time and must be loaded to compile the module. But it is not required at runtime.
|
|
|
* `i:` install-dependency: A install-dependency is required at runtime, but must not be loaded at runtime of the module. An example is the Intel compiler. It requires GCC but GCC must not be loaded. A install-dependency is loaded at build-time.
|
|
|
* no prefix: dependencies without prefix must be loaded at build- and runtime.
|
|
|
|
|
|
==== Variants file and overlays
|
|
|
|