forked from JCSDA/spack-stack
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
8786bba
commit 67c3ea9
Showing
3 changed files
with
43 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
.. _CreatingEnvironment: | ||
|
||
Creating and installing new environments | ||
**************************************** | ||
|
||
The following instructions are a simplified version of the instructions found in :numref:`Sections %s <NewSiteConfigs_macOS>` and :numref:`%s <NewSiteConfigs_Linux>`, and should work for most systems where spack-stack already has a site configuration, or where minimal configuration is necessary. For more detailed instructions, including how to generate new site configurations and more details of when and how to use external packages, see :numref:`Sections %s <NewSiteConfigs_macOS>` and :numref:`%s <NewSiteConfigs_Linux>`. To chain a new Spack environment to an existing one, such as to test a new package version based on dependencies already installed in the upstream environment, see :numref:`%s <Add_Test_Packages>`. | ||
|
||
Run the following steps in the case of a new release on a supported platform, or a fresh install on a local machine. Note that items in "<item>" should be replaced with the appropriate values (site names, etc.). "<site name>" and "<template name>" must match the names of directories found under 'configs/sites/' and 'configs/templates/', respectively; <environment name> is a user-chosen name for the Spack environment. | ||
|
||
.. code-block:: console | ||
# To generate a new spack-stack directory structure, run 'git clone --recurse-submodules https://github.com/JCSDA/spack-stack', | ||
# optionally with, e.g., '-b release/1.4.1' to specify the version | ||
. <path to spack-stack directory>/setup.sh | ||
spack stack create env --site <site name> --template <template name> --name <environment name> | ||
cd ${SPACK_STACK_DIR}/envs/<environment name>/ | ||
spack env activate . | ||
# If not using an existing site configuration, you may wish to modify config files and/or populate them using commands | ||
# such as 'spack external find' and 'spack compiler find'. | ||
# See https://spack-tutorial.readthedocs.io/en/latest/tutorial_configuration.html | ||
spack concretize |& tee log.concretize | ||
spack install [--verbose] [--fail-fast] |& tee log.install | ||
spack module lmod refresh | ||
spack stack setup-meta-modules |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters