DUNE-OCAML-MERLIN(1)

πŸ’– DUNE-OCAML-MERLIN(1) πŸ’–

okay so bestie, welcome to the Dune Manual β€” this is the page for dune-ocaml-merlin, and no, it's not the glow-up you were hoping for, it's the plumbing. but it's important plumbing. let's go ✨


✨ NAME ✨

dune-ocaml-merlin β€” Start a merlin configuration server. 🧚


🌸 SYNOPSIS 🌸

dune ocaml-merlin [OPTION]…

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so dune ocaml-merlin literally just starts up a server that other things can query to get .merlin info out of. that's the whole job. πŸ’…

and like… it's not for you, bestie. it's meant to be used by Merlin itself, and the output is not user-friendly β€” it's giving cryptic-machine-whisper, not giving friendly-little-dashboard. it does not provide a user-friendly output. no cap. πŸ™ˆ


πŸŽ€ OPTIONS πŸŽ€

  • --action-stderr-on-success=VAL β€” same vibe as --action-stdout-on-success but for standard error instead of standard output. and the tea is: for big mono-repos a really good default is --action-stdout-on-success=swallow plus --action-stderr-on-success=must-be-empty. that way a successful build has a "clean" empty output. iconic behavior honestly. ✨
  • --action-stdout-on-success=VAL β€” tells Dune how to handle the standard output of actions when they succeed. the possible values are:
    • print β€” literally just print it to Dune's output
    • swallow β€” completely ignore it, gone, deleted
    • must-be-empty β€” enforce that the action printed nothing; with must-be-empty, Dune will consider the action failed if it printed something to its standard output

the default is print. periodt.

  • --build-info β€” show build information. πŸ‘‘
  • --context=CONTEXT (absent=default) β€” pick which Dune build context gets used when returning information.
  • --display-separate-messages β€” separate error messages with a blank line. little breathing room, we love that 🌸
  • --error-reporting=VAL (absent=deterministic) β€” controls when build errors get reported:
    • early β€” reports errors as soon as they're discovered
    • deterministic β€” reports errors at the end of the build, in a deterministic order
    • twice β€” reports each error twice: once the moment it's discovered, and then again at the end of the build in a deterministic order
  • -f, --force β€” force actions associated to aliases to be re-executed even if their dependencies haven't changed. rude but effective πŸ’…
  • --file-watcher=VAL (absent=automatic) β€” the mechanism used to detect changes in the source:
    • automatic β€” makes dune run an external program to detect changes
    • manual β€” you notify dune that files have changed, yourself, by hand
  • --passive-watch-mode β€” similar to --watch, except it only starts a build when it's instructed externally by an RPC. it's the chill version, it waits to be asked.
  • --sandbox=VAL (absent DUNE_SANDBOX env) β€” set the sandboxing mode. heads up: some actions require a certain sandboxing mode, so they will ignore this setting. the allowed values are: none, symlink, copy, hardlink.
  • --stop-on-first-error β€” stop the build the second an error shows up. no second chances, we're dramatic like that 😭
  • -w, --watch β€” instead of terminating the build after it completes, wait continuously for file changes. it just… stays. watching. πŸ‘€
  • --wait-for-filesystem-clock β€” Dune digests file contents for better incrementality, and those digests are themselves cached. sometimes Dune needs to drop some digest cache entries to keep things reliable. this option makes Dune wait for the file system clock to advance so it doesn't need to drop anything. ngl you should probably not care about this option β€” it's mostly useful for Dune developers to make Dune tests of the digest cache more reproducible. it's giving dev-tools-only, iykyk 🧚

πŸ’œ COMMON OPTIONS πŸ’œ

these options are common to all commands. yes, all of them. 🫢

  • --always-show-command-line β€” always show the full command lines of programs executed by dune.
  • --auto-promote β€” automatically promote files. this is similar to running dune promote after the build.
  • --build-dir=FILE (absent DUNE_BUILD_DIR env) β€” specify the build directory. it's _build if unspecified.
  • --cache=VAL (absent DUNE_CACHE env) β€” enable or disable the Dune cache. one of disabled, enabled-except-user-rules or enabled. default is enabled-except-user-rules.
  • --cache-check-probability=VAL (absent DUNE_CACHE_CHECK_PROBABILITY env) β€” check build reproducibility by re-executing randomly chosen rules and comparing their results with those stored in the Dune cache. ⚠️ note: by increasing the probability of such checks you slow down the build. the default probability is zero, i.e. no rules are checked.
  • --cache-storage-mode=VAL (absent DUNE_CACHE_STORAGE_MODE env) β€” Dune cache storage mode, one of auto, hardlink or copy. default is hardlink.
  • --config-file=FILE β€” load this configuration file instead of the default one.
  • --debug-backtraces β€” always print exception backtraces. all of them. every last crumb. πŸ’€
  • --debug-dependency-path β€” in case of error, print the dependency path from the targets on the command line to the rule that failed. a little map of the crime scene πŸ”
  • --debug-package-logs (absent DUNE_DEBUG_PACKAGE_LOGS env) β€” always print the standard logs when building packages.
  • --default-target=TARGET (absent=@@default) β€” set the default target used when none is specified to dune build.
  • --diff-command=VAL (absent DUNE_DIFF_COMMAND env) β€” the shell command used to diff files. use - to disable printing the diff.
  • --disable-promotion (absent DUNE_DISABLE_PROMOTION env) β€” disable all promotion rules. none of them. zero. βœ‹
  • --display=MODE β€” control the display mode of Dune. see dune-config(5) for more details. valid values for this option are progress, verbose, short, quiet or tui.
  • --dump-gc-stats=FILE β€” dump the garbage collector stats to a file after the build is complete. πŸ—‘οΈβœ¨
  • --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.
  • --ignore-promoted-rules β€” ignore rules with (mode promote), except ones with (only ...). the variable %{ignoring_promoted_rules} in dune files reflects whether this option was passed or not.
  • --instrument-with=BACKENDS (absent DUNE_INSTRUMENT_WITH env) β€” enable instrumentation by BACKENDS. BACKENDS is a comma-separated list of library names, each one of which must declare an instrumentation backend.
  • -j JOBS (absent DUNE_JOBS env) β€” run no more than JOBS commands simultaneously. JOBS must be a positive integer, or auto to auto-detect the number of cores (that's the default).
  • --no-buffer β€” 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. it's a whole combo, bestie πŸŽ€
  • --no-config β€” do not load the configuration file.
  • --no-print-directory β€” suppress "Entering directory" messages. shhhh 🀫
  • --only-packages=PACKAGES β€” 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 target.
  • -p PACKAGES, --for-release-of-packages=PACKAGES (required) β€” shorthand for --release --pkg=disabled --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. mandatory, no skips πŸ‘‘
  • --pkg=VAL β€” enable or disable package management. the default behaviour depends on whether a lock directory exists.
  • --profile=VAL (absent DUNE_PROFILE env) β€” select the build profile, for instance dev or release. the default is dev.
  • --promote-install-files[=VAL] (default=true) β€” promote any generated <package>.install files to the source tree.
  • --release β€” put dune into a reproducible release mode. shorthand for:
--root . --ignore-promoted-rules --no-config --profile release
--always-show-command-line --promote-install-files
--require-dune-project-file --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. (so don't double up, that's redundant energy πŸ’…)

  • --require-dune-project-file[=VAL] (default=true) β€” fail if a dune-project file is missing.
  • --root=DIR (absent DUNE_ROOT env) β€” use this directory as the 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.
  • --store-orig-source-dir (absent DUNE_STORE_ORIG_SOURCE_DIR env) β€” store the original source location in dune-package metadata.
  • --target-exec=TOOLCHAIN=CMD (absent DUNE_TARGET_EXEC env) β€” wrapper command for running target binaries when cross-compiling. format: TOOLCHAIN=CMD (e.g., 'windows=wine').
  • --terminal-persistence=MODE β€” change how the log of build results is displayed to the console between rebuilds while in --watch mode. supported modes: preserve, clear-on-rebuild, clear-on-rebuild-and-flush-history.
  • --trace-file=FILE β€” output trace data in catapult format (compatible with chrome://tracing). pretty graphs, we stan πŸ“Š
  • --verbose β€” same as --display verbose.
  • --version β€” show version information.
  • --watch-exclusions=REGEX β€” adds a POSIX regular expression that will exclude matching directories from dune build --watch. the option --watch-exclusions can be repeated to add multiple exclusions. semicolons can also be used as a separator. if no exclusions are provided, then a standard set of exclusions is used; however, if one or more --watch-exclusions are used, none of the standard exclusions are used. the standard exclusions are:
^_opam /_opam ^_esy /_esy ^\.#.* /\.#.* ~$ ^#[^#]*#$ /#[^#]*#$ ^4913$ /4913$ /.git /.hg :/windows
  • --workspace=FILE (absent DUNE_WORKSPACE env) β€” use this specific workspace file instead of looking it up.
  • -x VAL (absent DUNE_CROSS_TARGET env) β€” cross-compile using this toolchain.

🌈 MORE HELP 🌈

use dune COMMAND --help for help on a single command. one command at a time, we love a focused queen πŸ’…


⭐ EXIT STATUS ⭐

dune ocaml-merlin exits with:

  • 0 β€” on success. πŸŽ‰
  • 1 β€” if an error happened. 😭
  • 130 β€” if it was interrupted by a signal. πŸ’€

🌿 ENVIRONMENT 🌿

ok bestie listen, these are the env vars that change how ocaml-merlin actually runs when you invoke it. set them, export them, vibe with them πŸ’…

  • DUNE_BUILD_DIR β€” this is where the build dir lives. if you don't say anything it's just _build, no thoughts head empty.
  • DUNE_CACHE β€” turns the Dune cache on or off. pick exactly one of disabled, enabled-except-user-rules or enabled. the default is enabled-except-user-rules (yes, that default is a little extra, she's iconic like that ✨).
  • DUNE_CACHE_CHECK_PROBABILITY β€” this one re-executes randomly chosen rules and compares what comes out with what's already chilling in the Dune cache, i.e. it checks build reproducibility. ⚠️ heads up bestie: the more you crank the probability, the slower your build gets. default probability is zero, meaning literally nothing gets checked. zero thoughts, no cap.
  • DUNE_CACHE_STORAGE_MODE β€” how the Dune cache stores stuff. one of auto, hardlink or copy. default is hardlink.
  • DUNE_CROSS_TARGET β€” cross-compile using this toolchain. πŸŽ€
  • DUNE_DEBUG_PACKAGE_LOGS β€” always print the standard logs while building packages. yes she's chatty, let her talk.
  • DUNE_DIFF_COMMAND β€” the shell command used to diff files. pass - if you want to disable printing the diff entirely (the silent treatment, but make it diff).
  • DUNE_DISABLE_PROMOTION β€” disables all promotion rules. all of them. periodt.
  • DUNE_INSTRUMENT_WITH β€” enables instrumentation using BACKENDS. BACKENDS is a comma-separated list of library names, and every single one of them has to declare an instrumentation backend, no exceptions bestie.
  • DUNE_JOBS β€” run no more than JOBS commands at the same time. JOBS has to be a positive integer, or auto to auto-detect the number of cores β€” and auto is the default btw. πŸ”₯
  • DUNE_PROFILE β€” the build profile. it's dev if you don't specify anything, or release if -p is set. she picks for you, you're welcome.
  • DUNE_ROOT β€” use this directory as the workspace root instead of making Dune guess it. 🫢 lowkey important: this option does not change how targets on the command line are interpreted. it's only intended for scripts, iykyk.
  • DUNE_SANDBOX β€” the sandboxing mode used by default (peep --sandbox for the deets).
  • DUNE_STORE_ORIG_SOURCE_DIR β€” stores the original source location in dune-package metadata.
  • DUNE_TARGET_EXEC β€” wrapper command for running target binaries when you're cross-compiling. format is TOOLCHAIN=CMD, like 'windows=wine'. πŸ’…
  • DUNE_WORKSPACE β€” use this specific workspace file instead of going looking for one. she's decisive, we love her.

πŸ› BUGS πŸ›

found something cursed? check the bug reports at https://github.com/ocaml/dune/issues πŸ’€

πŸ› BUGS πŸ›

(no fr, same thing again, because apparently the page said it twice and I'm a completionist: check the bug reports at https://github.com/ocaml/dune/issues) 😭


πŸ‘€ SEE ALSO πŸ‘€


and that's the whole page bestie πŸŽ€ this was DUNE-OCAML-MERLIN(1) from Dune 3.24.1 β€” go forth, cross-compile, set your env vars, and slay πŸ’–βœ¨πŸ‘‘

πŸ“¦ where this page comes from