1dune-compute(1) Dune Manual dune-compute(1)
2
3
4
6 dune-compute - Compute internal function.
7
9 dune compute [OPTION]... FUNCTION [INPUT]
10
12 Run a registered memoize function with the given input and print the
13 output.
14
15 This should only be used for debugging dune.
16
18 FUNCTION (required)
19 Compute FUNCTION for a given input.
20
21 INPUT
22 Use INPUT as the input to the function.
23
25 -f, --force
26 Force actions associated to aliases to be re-executed even if their
27 dependencies haven't changed.
28
29 --help[=FMT] (default=auto)
30 Show this help in format FMT. The value FMT must be one of `auto',
31 `pager', `groff' or `plain'. With `auto', the format is `pager` or
32 `plain' whenever the TERM env var is `dumb' or undefined.
33
34 --version
35 Show version information.
36
37 -w, --watch
38 Instead of terminating build after completion, wait continuously
39 for file changes.
40
42 These options are common to all commands.
43
44 --auto-promote
45 Automatically promote files. This is similar to running dune
46 promote after the build.
47
48 --build-dir=FILE (absent DUNE_BUILD_DIR env)
49 Specified build directory. _build if unspecified
50
51 --config-file=FILE
52 Load this configuration file instead of the default one.
53
54 --debug-backtraces
55 Always print exception backtraces.
56
57 --debug-dependency-path
58 In case of error, print the dependency path from the targets on the
59 command line to the rule that failed.
60
61 --debug-findlib
62 Debug the findlib sub-system.
63
64 --default-target=TARGET
65 Set the default target that when none is specified to dune build.
66 It defaults to @@default.
67
68 --dev
69 Same as --profile dev
70
71 --diff-command=VAL
72 Shell command to use to diff files. Use - to disable printing the
73 diff.
74
75 --display=MODE
76 Control the display mode of Dune. See dune-config(5) for more
77 details.
78
79 --ignore-promoted-rules
80 Ignore rules with (mode promote)
81
82 -j JOBS
83 Run no more than JOBS commands simultaneously.
84
85 --no-buffer
86 Do not buffer the output of commands executed by dune. By default
87 dune buffers the output of subcommands, in order to prevent
88 interleaving when multiple commands are executed in parallel.
89 However, this can be an issue when debugging long running tests.
90 With --no-buffer, commands have direct access to the terminal. Note
91 that as a result their output won't be captured in the log file.
92 You should use this option in conjunction with -j 1, to avoid
93 interleaving. Additionally you should use --verbose as well, to
94 make sure that commands are printed before they are being executed.
95
96 --no-config
97 Do not load the configuration file
98
99 --no-print-directory
100 Suppress "Entering directory" messages
101
102 --only-packages=PACKAGES
103 Ignore stanzas referring to a package that is not in PACKAGES.
104 PACKAGES is a comma-separated list of package names. Note that this
105 has the same effect as deleting the relevant stanzas from jbuild
106 files. It is mostly meant for releases. During development, it is
107 likely that what you want instead is to build a particular
108 <package>.install target.
109
110 -p PACKAGES, --for-release-of-packages=PACKAGES
111 Shorthand for --root . --only-packages PACKAGE
112 --ignore-promoted-rules --no-config --profile release. You must use
113 this option in your <package>.opam files, in order to build only
114 what's necessary when your project contains multiple packages as
115 well as getting reproducible builds.
116
117 --profile=VAL (absent DUNE_PROFILE env)
118 Select the build profile, for instance dev or release. The default
119 is dev.
120
121 --root=DIR
122 Use this directory as workspace root instead of guessing it. Note
123 that this option doesn't change the interpretation of targets given
124 on the command line. It is only intended for scripts.
125
126 --store-orig-source-dir (absent DUNE_STORE_ORIG_SOURCE_DIR env)
127 Store original source location in dune-package metadata
128
129 --trace-file=FILE
130 Output trace data in catapult format (compatible with
131 chrome://tracing)
132
133 --verbose
134 Same as --display verbose
135
136 --workspace=FILE
137 Use this specific workspace file instead of looking it up.
138
139 -x VAL
140 Cross-compile using this toolchain.
141
143 Use `dune COMMAND --help' for help on a single command.
144
146 These environment variables affect the execution of compute:
147
148 DUNE_BUILD_DIR
149 Specified build directory. _build if unspecified
150
151 DUNE_PROFILE
152 Build profile. dev if unspecified or release if -p is set.
153
154 DUNE_STORE_ORIG_SOURCE_DIR
155 Store original source location in dune-package metadata
156
158 Check bug reports at https://github.com/ocaml/dune/issues
159
160
161
162Dune 11VERSION11 dune-compute(1)