docs: jobserver & generated makefiles (#30526)
This commit is contained in:
parent
afc2d4284a
commit
2f14695882
1 changed files with 7 additions and 5 deletions
|
@ -950,12 +950,14 @@ A typical workflow is as follows:
|
||||||
spack -e . add perl
|
spack -e . add perl
|
||||||
spack -e . concretize
|
spack -e . concretize
|
||||||
spack -e . env depfile > Makefile
|
spack -e . env depfile > Makefile
|
||||||
make -j8
|
make -j64
|
||||||
|
|
||||||
This creates an environment in the current working directory, and after
|
This generates a ``Makefile`` from a concretized environment in the
|
||||||
concretization, generates a ``Makefile``. Then ``make`` starts at most
|
current working directory, and ``make -j64`` installs the environment,
|
||||||
8 concurrent jobs, meaning that multiple ``spack install`` processes may
|
exploiting parallelism across packages as much as possible. Spack
|
||||||
start.
|
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:
|
By default the following phony convenience targets are available:
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue