@@ -117,8 +117,8 @@ dependencies. See the
117
117
[ build command section of the user guide] ( GUIDE.md#the-build-command ) for
118
118
details of how these dependencies get specified.
119
119
120
- In addition to specifying targets, you can also control what gets built with the
121
- following flags:
120
+ In addition to specifying targets, you can also control what gets built, or
121
+ retained, with the following flags:
122
122
123
123
* ` --haddock ` , to build documentation. This may cause a lot of packages to get
124
124
re-built, so that the documentation links work.
@@ -140,13 +140,17 @@ following flags:
140
140
* ` --keep-going ` , to continue building packages even after some build step
141
141
fails. The packages which depend upon the failed build won't get built.
142
142
143
+ * ` --keep-tmp-files ` , to keep intermediate files and build directories that
144
+ would otherwise be considered temporary and deleted. It may be useful to
145
+ inspect these, if a build fails. By default, they are not kept.
146
+
143
147
* ` --skip ` , to skip building components of a local package. It allows
144
148
you to skip test suites and benchmark without specifying other components
145
149
(e.g. ` stack test --skip long-test-suite ` will run the tests without the
146
150
` long-test-suite ` test suite). Be aware that skipping executables won't work
147
- the first time the package is built due to
151
+ the first time the package is built due to
148
152
[ an issue in cabal] ( https://github.com/commercialhaskell/stack/issues/3229 ) .
149
- This option can be specified multiple times to skip multiple components.
153
+ This option can be specified multiple times to skip multiple components.
150
154
151
155
## Flags
152
156
0 commit comments