-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated existing docs on how to build on top of EESSI to use EESSI-extend
#316
Conversation
Co-authored-by: ocaisa <[email protected]>
…ch scenarios the EESSI-extend module should be loaded in order to have additionally installed modules available (i.e. when it was a project or user installation)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One note would be that EESSI_PROJECT_INSTALL
and EESSI_USER_INSTALL
are set to a path, and this is the path where installations are made. With this approach you can have multiple projects with different shared software stacks
Co-authored-by: ocaisa <[email protected]>
…ation easier and more explicit
This now depends on EESSI/software-layer#778 |
Better note that in the PR description... |
…l just have to make sure
This now depends on
EESSI-extend
to useEESSI_SITE_SOFTWARE_PATH
software-layer#778