Scroll to navigation

dune-install(1) Dune Manual dune-install(1)


dune-install - Install packages.


dune install [OPTION]... [PACKAGE]...


--destdir=PATH (absent DESTDIR env)
When passed, this directory is prepended to all installed paths.
Only display the file operations that would be performed.
-f, --force
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.
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 destdir
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.
Show version information.
-w, --watch
Instead of terminating build after completion, wait continuously for file changes.


These options are common to all commands.
Automatically promote files. This is similar to running dune promote after the build.
--build-dir=FILE (absent DUNE_BUILD_DIR env)
Specified build directory. _build if unspecified
Load this configuration file instead of the default one.
Always print exception backtraces.
In case of error, print the dependency path from the targets on the command line to the rule that failed.
Debug the findlib sub-system.
Set the default target that when none is specified to dune build. It defaults to @@default.
Same as --profile dev
Shell command to use to diff files. Use - to disable printing the diff.
Control the display mode of Dune. See dune-config(5) for more details.
Ignore rules with (mode promote)
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
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 jbuild 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.
-p PACKAGES, --for-release-of-packages=PACKAGES
Shorthand for --root . --only-packages PACKAGE --ignore-promoted-rules --no-config --profile release. 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.
Select the build profile, for instance dev or release. The default is dev.
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.
Record and print statistics about Dune resource usage.
Same as --display verbose
Use this specific workspace file instead of looking it up.
-x VAL
Cross-compile using this toolchain.


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


These environment variables affect the execution of install:
See option --destdir.
Specified build directory. _build if unspecified


Check bug reports at
Dune 1.6.2