You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**IMPORTANT: Steps 1, 2, and 3 need to be repeated for each
183
186
compiler/MPI combination that you wish to install.** The new
@@ -270,7 +273,7 @@ default is to use `$HOME/opt` and `config/config_custom.sh`
270
273
respectively. `<yaml>` represents a user configurable yaml file
271
274
containing a list of packages that need to be built in the stack along
272
275
with their versions and package options. The default value of `<yaml>`
273
-
is `config/stack_custom.yaml`.
276
+
is `stack/stack_custom.yaml`.
274
277
275
278
## Additional Notes:
276
279
@@ -303,9 +306,11 @@ template
303
306
2. define a new section in the `yaml` file for that library/package in
304
307
config directory
305
308
306
-
3. Add a call to the new build script in `build_stack.sh`
309
+
3. if the package is a python virtual environment, add a `requirements.txt` file listing the python packages required to install the package in `pyvenv/package_name.txt`
310
+
311
+
4. Add a call to the new build script in `build_stack.sh`
307
312
308
-
4. Create a new module template at the appropriate place in the
313
+
5. Create a new module template at the appropriate place in the
309
314
modulefiles directory, using exising files as a template
0 commit comments