1dune-clean(1)                     Dune Manual                    dune-clean(1)
2
3
4

NAME

6       dune-clean - Clean the project.
7

SYNOPSIS

9       dune clean [OPTION]...
10

DESCRIPTION

12       Removes files added by dune such as _build, <package>.install, and
13       .merlin
14

OPTIONS

16       -f, --force
17           Force actions associated to aliases to be re-executed even if their
18           dependencies haven't changed.
19
20       --help[=FMT] (default=auto)
21           Show this help in format FMT. The value FMT must be one of `auto',
22           `pager', `groff' or `plain'. With `auto', the format is `pager` or
23           `plain' whenever the TERM env var is `dumb' or undefined.
24
25       --version
26           Show version information.
27

COMMON OPTIONS

29       These options are common to all commands.
30
31       --auto-promote
32           Automatically promote files. This is similar to running dune
33           promote after the build.
34
35       --build-dir=FILE (absent DUNE_BUILD_DIR env)
36           Specified build directory. _build if unspecified
37
38       --config-file=FILE
39           Load this configuration file instead of the default one.
40
41       --debug-backtraces
42           Always print exception backtraces.
43
44       --debug-dependency-path
45           In case of error, print the dependency path from the targets on the
46           command line to the rule that failed.
47
48       --debug-findlib
49           Debug the findlib sub-system.
50
51       --default-target=TARGET
52           Set the default target that when none is specified to dune build.
53           It defaults to @@default.
54
55       --dev
56           Same as --profile dev
57
58       --diff-command=VAL
59           Shell command to use to diff files
60
61       --display=MODE
62           Control the display mode of Dune. See dune-config(5) for more
63           details.
64
65       --ignore-promoted-rules
66           Ignore rules with (mode promote)
67
68       -j JOBS
69           Run no more than JOBS commands simultaneously.
70
71       --no-buffer
72           Do not buffer the output of commands executed by dune. By default
73           dune buffers the output of subcommands, in order to prevent
74           interleaving when multiple commands are executed in parallel.
75           However, this can be an issue when debugging long running tests.
76           With --no-buffer, commands have direct access to the terminal. Note
77           that as a result their output won't be captured in the log file.
78           You should use this option in conjunction with -j 1, to avoid
79           interleaving. Additionally you should use --verbose as well, to
80           make sure that commands are printed before they are being executed.
81
82       --no-config
83           Do not load the configuration file
84
85       --only-packages=PACKAGES
86           Ignore stanzas referring to a package that is not in PACKAGES.
87           PACKAGES is a comma-separated list of package names. Note that this
88           has the same effect as deleting the relevant stanzas from jbuild
89           files. It is mostly meant for releases. During development, it is
90           likely that what you want instead is to build a particular
91           <package>.install target.
92
93       -p PACKAGES, --for-release-of-packages=PACKAGES
94           Shorthand for --root . --only-packages PACKAGE --promote ignore
95           --no-config --profile release. You must use this option in your
96           <package>.opam files, in order to build only what's necessary when
97           your project contains multiple packages as well as getting
98           reproducible builds.
99
100       --profile=VAL
101           Select the build profile, for instance dev or release. The default
102           is dev.
103
104       --root=DIR
105           Use this directory as workspace root instead of guessing it. Note
106           that this option doesn't change the interpretation of targets given
107           on the command line. It is only intended for scripts.
108
109       --verbose
110           Same as --display verbose
111
112       --workspace=FILE
113           Use this specific workspace file instead of looking it up.
114
115       -x VAL
116           Cross-compile using this toolchain.
117

MORE HELP

119       Use `dune COMMAND --help' for help on a single command.
120

ENVIRONMENT

122       These environment variables affect the execution of clean:
123
124       DUNE_BUILD_DIR
125           Specified build directory. _build if unspecified
126

BUGS

128       Check bug reports at https://github.com/ocaml/dune/issues
129
130
131
132Dune 11VERSION11                                                 dune-clean(1)
Impressum