1dune-utop(1) Dune Manual dune-utop(1)
2
6 dune-utop - Load library in utop
7
9 dune utop [OPTION]... [PATH] [ARGS]...
10
12 dune utop DIR build and run utop toplevel with libraries defined in DIR
13
15 --context=CONTEXT (absent=default)
16 Select context where to build/run utop.
17 -f, --force
19 Force actions associated to aliases to be re-executed even if their
20 dependencies haven't changed.
21 --help[=FMT] (default=auto)
23 Show this help in format FMT. The value FMT must be one of `auto',
24 `pager', `groff' or `plain'. With `auto', the format is `pager` or
25 `plain' whenever the TERM env var is `dumb' or undefined.
26 --version
28 Show version information.
29
31 These options are common to all commands.
32 --auto-promote
34 Automatically promote files. This is similar to running dune
35 promote after the build.
36 --build-dir=FILE (absent DUNE_BUILD_DIR env)
38 Specified build directory. _build if unspecified
39 --config-file=FILE
41 Load this configuration file instead of the default one.
42 --debug-backtraces
44 Always print exception backtraces.
45 --debug-dependency-path
47 In case of error, print the dependency path from the targets on the
48 command line to the rule that failed.
49 --debug-findlib
51 Debug the findlib sub-system.
52 --default-target=TARGET
54 Set the default target that when none is specified to dune build.
55 It defaults to @@default.
56 --dev
58 Same as --profile dev
59 --diff-command=VAL
61 Shell command to use to diff files
62 --display=MODE
64 Control the display mode of Dune. See dune-config(5) for more
65 details.
66 --ignore-promoted-rules
68 Ignore rules with (mode promote)
69 -j JOBS
71 Run no more than JOBS commands simultaneously.
72 --no-buffer
74 Do not buffer the output of commands executed by dune. By default
75 dune buffers the output of subcommands, in order to prevent
76 interleaving when multiple commands are executed in parallel.
77 However, this can be an issue when debugging long running tests.
78 With --no-buffer, commands have direct access to the terminal. Note
79 that as a result their output won't be captured in the log file.
80 You should use this option in conjunction with -j 1, to avoid
81 interleaving. Additionally you should use --verbose as well, to
82 make sure that commands are printed before they are being executed.
83 --no-config
85 Do not load the configuration file
86 --only-packages=PACKAGES
88 Ignore stanzas referring to a package that is not in PACKAGES.
89 PACKAGES is a comma-separated list of package names. Note that this
90 has the same effect as deleting the relevant stanzas from jbuild
91 files. It is mostly meant for releases. During development, it is
92 likely that what you want instead is to build a particular
93 <package>.install target.
94 -p PACKAGES, --for-release-of-packages=PACKAGES
96 Shorthand for --root . --only-packages PACKAGE --promote ignore
97 --no-config --profile release. You must use this option in your
98 <package>.opam files, in order to build only what's necessary when
99 your project contains multiple packages as well as getting
100 reproducible builds.
101 --profile=VAL
103 Select the build profile, for instance dev or release. The default
104 is dev.
105 --root=DIR
107 Use this directory as workspace root instead of guessing it. Note
108 that this option doesn't change the interpretation of targets given
109 on the command line. It is only intended for scripts.
110 --verbose
112 Same as --display verbose
113 --workspace=FILE
115 Use this specific workspace file instead of looking it up.
116 -x VAL
118 Cross-compile using this toolchain.
119
121 Use `dune COMMAND --help' for help on a single command.
122
124 These environment variables affect the execution of utop:
125 DUNE_BUILD_DIR
127 Specified build directory. _build if unspecified
128
130 Check bug reports at https://github.com/ocaml/dune/issues
131Dune 11VERSION11 dune-utop(1)