Force actions associated to aliases to be re-executed even if their
dependencies haven't changed.
--help[=FMT] (default=auto)
Show this help in format FMT. The value FMT must be one of
`auto', `pager', `groff' or `plain'. With `auto', the format is `pager` or
`plain' whenever the TERM env var is `dumb' or undefined.
--sandbox=VAL (absent DUNE_SANDBOX env)
Sandboxing mode to use by default. Some actions require a certain
sandboxing mode, so they will ignore this setting. The allowed values are:
none, symlink, copy.
--version
Show version information.
-w, --watch
Instead of terminating build after completion, wait continuously for file
changes.
Control the display mode of Dune. See dune-config(5) for more
details.
--ignore-promoted-rules
Ignore rules with (mode promote), except ones with (only ...). The
variable %{ignoring_promoted_rules} in dune files reflects whether this
option was passed or not.
"Enable instrumentation by BACKENDS. BACKENDS is a
comma-separated list of library names, each one of which must declare an
instrumentation backend.
-jJOBS
Run no more than JOBS commands simultaneously.
--no-buffer
Do not buffer the output of commands executed by dune. By default dune
buffers the output of subcommands, in order to prevent interleaving when
multiple commands are executed in parallel. However, this can be an issue
when debugging long running tests. With --no-buffer, commands have
direct access to the terminal. Note that as a result their output won't be
captured in the log file. You should use this option in conjunction with
-j 1, to avoid interleaving. Additionally you should use
--verbose as well, to make sure that commands are printed before
they are being executed.
--no-config
Do not load the configuration file
--no-print-directory
Suppress "Entering directory" messages
--only-packages=PACKAGES
Ignore stanzas referring to a package that is not in PACKAGES.
PACKAGES is a comma-separated list of package names. Note that this
has the same effect as deleting the relevant stanzas from dune files. It
is mostly meant for releases. During development, it is likely that what
you want instead is to build a particular <package>.install
target.
-pPACKAGES,
--for-release-of-packages=PACKAGES
Shorthand for --release --only-packages PACKAGE. You must use this
option in your <package>.opam files, in order to build only
what's necessary when your project contains multiple packages as well as
getting reproducible builds.
--profile=VAL (absent DUNE_PROFILE env)
Select the build profile, for instance dev or release. The
default is dev.
--promote-install-files
Promote the generated <package>.install files to the source
tree
--release
Put dune into a reproducible release mode. This is in fact a
shorthand for --root . --ignore-promoted-rules --no-config --profile
release --always-show-command-line --promote-install-files
--default-target @install. You should use this option for release
builds. For instance, you must use this option in your
<package>.opam files. Except if you already use -p, as
-p implies this option.
--root=DIR
Use this directory as workspace root instead of guessing it. Note that
this option doesn't change the interpretation of targets given on the
command line. It is only intended for scripts.