diff options
author | Ivan Mincik <ivan.mincik@gmail.com> | 2023-11-19 23:34:11 +0100 |
---|---|---|
committer | Ivan Mincik <ivan.mincik@gmail.com> | 2023-11-20 00:06:11 +0100 |
commit | 57801428da59dbd35e9c06846023c2dfee36732d (patch) | |
tree | e1f3a05e670b86b00b5d55eb5b79dab098dec530 /doc/stdenv | |
parent | 8314afe1725e064a483e0e7d96b657c89a6c67f0 (diff) |
doc/stdenv: update manual phases execution instructions
Update instructions for manual build phases execution via `nix-shell` to cover all phases. There is no easy way of getting those commands, so it makes a sense to have them all properly documented.
Diffstat (limited to 'doc/stdenv')
-rw-r--r-- | doc/stdenv/stdenv.chapter.md | 11 |
1 files changed, 8 insertions, 3 deletions
diff --git a/doc/stdenv/stdenv.chapter.md b/doc/stdenv/stdenv.chapter.md index 26c43bd9e943c..03bb8a9ff790e 100644 --- a/doc/stdenv/stdenv.chapter.md +++ b/doc/stdenv/stdenv.chapter.md @@ -119,13 +119,18 @@ phases="${prePhases[*]:-} unpackPhase patchPhase" genericBuild ``` Then, run more phases up until the failure is reached. -For example, if the failure is in the build phase, the following phases would be required: +If the failure is in the build or check phase, the following phases would be required: ```bash -phases="${preConfigurePhases[*]:-} configurePhase ${preBuildPhases[*]:-} buildPhase" genericBuild +phases="${preConfigurePhases[*]:-} configurePhase ${preBuildPhases[*]:-} buildPhase checkPhase" genericBuild ``` -Re-run a single phase as many times as necessary to examine the failure like so: +Use this command to run all install phases: +```bash +phases="${preInstallPhases[*]:-} installPhase ${preFixupPhases[*]:-} fixupPhase installCheckPhase" genericBuild +``` + +Single phase can be re-run as many times as necessary to examine the failure like so: ```bash phases="buildPhase" genericBuild |