diff options
| author | Harmen Stoppels <harmenstoppels@gmail.com> | 2022-07-05 14:48:32 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-07-05 14:48:32 +0200 |
| commit | dac31ef3c405709aadd467eab21686f5a51930db (patch) | |
| tree | 1a9599101a6339c2e038bb8f516fadab9823f3b4 /lib/spack/docs/environments.rst | |
| parent | bb3a663392edebb1f9918393a875dc3b5db2c995 (diff) | |
| download | spack-dac31ef3c405709aadd467eab21686f5a51930db.tar.gz spack-dac31ef3c405709aadd467eab21686f5a51930db.tar.bz2 spack-dac31ef3c405709aadd467eab21686f5a51930db.tar.xz spack-dac31ef3c405709aadd467eab21686f5a51930db.zip | |
Remove fetch from depfile (#31433)
Diffstat (limited to 'lib/spack/docs/environments.rst')
| -rw-r--r-- | lib/spack/docs/environments.rst | 20 |
1 files changed, 8 insertions, 12 deletions
diff --git a/lib/spack/docs/environments.rst b/lib/spack/docs/environments.rst index 62ec2f74f7..ee95d4f779 100644 --- a/lib/spack/docs/environments.rst +++ b/lib/spack/docs/environments.rst @@ -1013,7 +1013,7 @@ The following advanced example shows how generated targets can be used in a SPACK ?= spack - .PHONY: all clean fetch env + .PHONY: all clean env all: env @@ -1022,9 +1022,6 @@ The following advanced example shows how generated targets can be used in a env.mk: spack.lock $(SPACK) -e . env depfile -o $@ --make-target-prefix spack - - fetch: spack/fetch - $(info Environment fetched!) env: spack/env $(info Environment installed!) @@ -1037,10 +1034,10 @@ The following advanced example shows how generated targets can be used in a endif When ``make`` is invoked, it first "remakes" the missing include ``env.mk`` -from its rule, which triggers concretization. When done, the generated targets -``spack/fetch`` and ``spack/env`` are available. In the above -example, the ``env`` target uses the latter as a prerequisite, meaning -that it can make use of the installed packages in its commands. +from its rule, which triggers concretization. When done, the generated target +``spack/env`` is available. In the above example, the ``env`` target uses this generated +target as a prerequisite, meaning that it can make use of the installed packages in +its commands. As it is typically undesirable to remake ``env.mk`` as part of ``make clean``, the include is conditional. @@ -1048,7 +1045,6 @@ the include is conditional. .. note:: When including generated ``Makefile``\s, it is important to use - the ``--make-target-prefix`` flag and use the non-phony targets - ``<target-prefix>/env`` and ``<target-prefix>/fetch`` as - prerequisites, instead of the phony targets ``<target-prefix>/all`` - and ``<target-prefix>/fetch-all`` respectively. + the ``--make-target-prefix`` flag and use the non-phony target + ``<target-prefix>/env`` as prerequisite, instead of the phony target + ``<target-prefix>/all``. |