Select context to install from. By default, install files from all defined
--destdir=PATH (absent DESTDIR env)
When passed, this directory is prepended to all installed paths.
Only display the file operations that would be performed.
Force actions associated to aliases to be re-executed even if their
dependencies haven't changed.
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.
Directory where library files are copied, relative to prefix or
absolute. If --prefix is specified the default is
$prefix/lib, otherwise it is the output of ocamlfind printconf
When passed, manually override the directory to install man pages
Directory where files are copied. For instance binaries are copied into
$prefix/bin, library files into $prefix/lib, etc... It
defaults to the current opam prefix if opam is available and configured,
otherwise it uses the same prefix as the ocaml compiler.
Make the binaries relocatable (the installation directory can be
--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.
sections that should be installed
Show version information.
Instead of terminating build after completion, wait continuously for file
"Enable instrumentation by BACKENDS. BACKENDS is a
comma-separated list of library names, each one of which must declare an
Run no more than JOBS commands simultaneously.
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.
Do not load the configuration file
Suppress "Entering directory" messages
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
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 the generated <package>.install files to the source
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.
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.