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
Copy file name to clipboardExpand all lines: tutorial_developer_workflows.rst
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -314,13 +314,13 @@ Developers can achieve builds of both cases from a single ``spack install`` as l
314
314
315
315
.. code-block:: console
316
316
317
-
# First we have to allow repeat specs in the environment
318
-
$ spack config add concretizer:unify:false
319
-
# Next we need to specify the specs we want ('==' propagates the variant to deps)
320
-
$ spack change macsio build_type==Release
321
-
$ spack add macsio+scr build_type==Debug
322
-
# Inspect the graph for multiple dev_path=
323
-
$ spack concretize -f
317
+
# First we have to allow repeat specs in the environment
318
+
$ spack config add concretizer:unify:false
319
+
# Next we need to specify the specs we want ('==' propagates the variant to deps)
320
+
$ spack change macsio build_type==Release
321
+
$ spack add macsio+scr build_type==Debug
322
+
# Inspect the graph for multiple dev_path=
323
+
$ spack concretize -f
324
324
325
325
While we won't build out this example it illustrates how the ``dev_path`` for ``build_type=Release`` and ``build_type=Debug`` points to the same source code.
0 commit comments