1dune-installed-libraries(1) Dune Manual dune-installed-libraries(1)
2
6 dune-installed-libraries - Print out libraries installed on the system.
7
9 dune installed-libraries [OPTION]...
10
12 -f, --force
13 Force actions associated to aliases to be re-executed even if their
14 dependencies haven't changed.
15 --help[=FMT] (default=auto)
17 Show this help in format FMT. The value FMT must be one of `auto',
18 `pager', `groff' or `plain'. With `auto', the format is `pager` or
19 `plain' whenever the TERM env var is `dumb' or undefined.
20 --not-available, --na
22 List libraries that are not available and explain why
23 --version
25 Show version information.
26
28 --auto-promote
29 Automatically promote files. This is similar to running dune
30 promote after the build.
31 --build-dir=FILE (absent DUNE_BUILD_DIR env)
33 Specified build directory. _build if unspecified
34 --config-file=FILE
36 Load this configuration file instead of the default one.
37 --debug-backtraces
39 Always print exception backtraces.
40 --debug-dependency-path
42 In case of error, print the dependency path from the targets on the
43 command line to the rule that failed.
44 --debug-findlib
46 Debug the findlib sub-system.
47 --default-target=TARGET
49 Set the default target that when none is specified to dune build.
50 It defaults to @@default.
51 --dev
53 Same as --profile dev
54 --diff-command=VAL
56 Shell command to use to diff files
57 --display=MODE
59 Control the display mode of Dune. See dune-config(5) for more
60 details.
61 --ignore-promoted-rules
63 Ignore rules with (mode promote)
64 -j JOBS
66 Run no more than JOBS commands simultaneously.
67 --no-buffer
69 Do not buffer the output of commands executed by dune. By default
70 dune buffers the output of subcommands, in order to prevent
71 interleaving when multiple commands are executed in parallel.
72 However, this can be an issue when debugging long running tests.
73 With --no-buffer, commands have direct access to the terminal. Note
74 that as a result their output won't be captured in the log file.
75 You should use this option in conjunction with -j 1, to avoid
76 interleaving. Additionally you should use --verbose as well, to
77 make sure that commands are printed before they are being executed.
78 --no-config
80 Do not load the configuration file
81 --only-packages=PACKAGES
83 Ignore stanzas referring to a package that is not in PACKAGES.
84 PACKAGES is a comma-separated list of package names. Note that this
85 has the same effect as deleting the relevant stanzas from jbuild
86 files. It is mostly meant for releases. During development, it is
87 likely that what you want instead is to build a particular
88 <package>.install target.
89 -p PACKAGES, --for-release-of-packages=PACKAGES
91 Shorthand for --root . --only-packages PACKAGE --promote ignore
92 --no-config --profile release. You must use this option in your
93 <package>.opam files, in order to build only what's necessary when
94 your project contains multiple packages as well as getting
95 reproducible builds.
96 --profile=VAL
98 Select the build profile, for instance dev or release. The default
99 is dev.
100 --root=DIR
102 Use this directory as workspace root instead of guessing it. Note
103 that this option doesn't change the interpretation of targets given
104 on the command line. It is only intended for scripts.
105 --verbose
107 Same as --display verbose
108 --workspace=FILE
110 Use this specific workspace file instead of looking it up.
111 -x VAL
113 Cross-compile using this toolchain.
114
116 These environment variables affect the execution of
117 installed-libraries:
118 DUNE_BUILD_DIR
120 Specified build directory. _build if unspecified
121Dune 11VERSION11 dune-installed-libraries(1)