1.1 --- a/docs/overview.txt Mon Oct 12 19:31:50 2009 +0200
1.2 +++ b/docs/overview.txt Wed Dec 30 15:36:22 2009 +0100
1.3 @@ -366,22 +366,22 @@
1.4
1.5 If you want to stop the build after a step you are debugging, you can pass the
1.6 variable STOP to make:
1.7 - ct-ng STOP=some_step
1.8 + ct-ng build STOP=some_step
1.9
1.10 Conversely, if you want to restart a build at a specific step you are
1.11 debugging, you can pass the RESTART variable to make:
1.12 - ct-ng RESTART=some_step
1.13 + ct-ng build RESTART=some_step
1.14
1.15 Alternatively, you can call make with the name of a step to just do that step:
1.16 ct-ng libc_headers
1.17 is equivalent to:
1.18 - ct-ng RESTART=libc_headers STOP=libc_headers
1.19 + ct-ng build RESTART=libc_headers STOP=libc_headers
1.20
1.21 The shortcuts +step_name and step_name+ allow to respectively stop or restart
1.22 at that step. Thus:
1.23 - ct-ng +libc_headers and: ct-ng libc_headers+
1.24 + ct-ng +libc_headers and: ct-ng libc_headers+
1.25 are equivalent to:
1.26 - ct-ng STOP=libc_headers and: ct-ng RESTART=libc_headers
1.27 + ct-ng build STOP=libc_headers and: ct-ng build RESTART=libc_headers
1.28
1.29 To obtain the list of acceptable steps, please call:
1.30 ct-ng list-steps