From 2f14695882df11b831a7b804f9f8064c4ddfcfe9 Mon Sep 17 00:00:00 2001 From: Harmen Stoppels Date: Fri, 6 May 2022 14:04:48 +0200 Subject: docs: jobserver & generated makefiles (#30526) --- lib/spack/docs/environments.rst | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) (limited to 'lib') 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: -- cgit v1.2.3-70-g09d2