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