From b113edeab780216b0590045b932be685d1399e9b Mon Sep 17 00:00:00 2001 From: Eelco Dolstra Date: Fri, 25 Jun 2004 15:36:09 +0000 Subject: * A flag `--keep-going / -k' to keep building goals if one fails, as much as possible. (This is similar to GNU Make's `-k' flag.) * Refactoring to implement this: previously we just bombed out when a build failed, but now we have to clean up. In particular this means that goals must be freed quickly --- they shouldn't hang around until the worker exits. So the worker now maintains weak pointers in order not to prevent garbage collection. * Documented the `-k' and `-j' flags. --- doc/manual/opt-common.xml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) (limited to 'doc/manual/opt-common.xml') diff --git a/doc/manual/opt-common.xml b/doc/manual/opt-common.xml index 6c8db2a72757..158e282fdb55 100644 --- a/doc/manual/opt-common.xml +++ b/doc/manual/opt-common.xml @@ -108,6 +108,33 @@ + + / + + + Sets the maximum number of build jobs that Nix will perform in + parallel to the specified number. The default is 1. A higher + value is useful on SMP systems or to exploit I/O latency. + + + + + + + / + + + Keep going in case of failed builds, to the greatest extent + possible. That is, if building an input of some derivation + fails, Nix will still build the other inputs, but not the + derivation itself. Without this option, Nix stops if any build + fails (except for builds of substitutes), possibly killing + builds in progress (in case of parallel or distributed builds). + + + + + / -- cgit 1.4.1