summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorHarmen Stoppels <harmenstoppels@gmail.com>2022-05-06 14:04:48 +0200
committerGitHub <noreply@github.com>2022-05-06 14:04:48 +0200
commit2f14695882df11b831a7b804f9f8064c4ddfcfe9 (patch)
treec57ae986c39064cc5150e6cf8be58268a0a87167
parentafc2d4284a46d7f24df0f5127a3546259859855b (diff)
downloadspack-2f14695882df11b831a7b804f9f8064c4ddfcfe9.tar.gz
spack-2f14695882df11b831a7b804f9f8064c4ddfcfe9.tar.bz2
spack-2f14695882df11b831a7b804f9f8064c4ddfcfe9.tar.xz
spack-2f14695882df11b831a7b804f9f8064c4ddfcfe9.zip
docs: jobserver & generated makefiles (#30526)
-rw-r--r--lib/spack/docs/environments.rst14
1 files changed, 8 insertions, 6 deletions
diff --git a/lib/spack/docs/environments.rst b/lib/spack/docs/environments.rst
index 5b7a31d6ef..7744dc87e6 100644
--- a/lib/spack/docs/environments.rst
+++ b/lib/spack/docs/environments.rst
@@ -950,12 +950,14 @@ A typical workflow is as follows:
spack -e . add perl
spack -e . concretize
spack -e . env depfile > Makefile
- make -j8
-
-This creates an environment in the current working directory, and after
-concretization, generates a ``Makefile``. Then ``make`` starts at most
-8 concurrent jobs, meaning that multiple ``spack install`` processes may
-start.
+ make -j64
+
+This generates a ``Makefile`` from a concretized environment in the
+current working directory, and ``make -j64`` installs the environment,
+exploiting parallelism across packages as much as possible. Spack
+respects the Make jobserver and forwards it to the build environment
+of packages, meaning that a single ``-j`` flag is enough to control the
+load, even when packages are built in parallel.
By default the following phony convenience targets are available: