GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages
DUNE(1) Dune Manual DUNE(1)

dune - composable build system for OCaml

dune build [--watch]

dune runtest [--watch]

dune exec NAME

dune utop [DIR]

dune install

dune init project NAME [PATH] [--libs=l1,l2 --ppx=p1,p2 --inline-tests]

Dune is a build system designed for OCaml projects only. It focuses on providing the user with a consistent experience and takes care of most of the low-level details of OCaml compilation. All you have to do is provide a description of your project and Dune will do the rest.

The scheme it implements is inspired from the one used inside Jane Street and adapted to the open source world. It has matured over a long time and is used daily by hundreds of developers, which means that it is highly tested and productive.

An alias for promotion apply.
An alias for runtest.

Build the given targets, or all installable targets if none are given.
Manage the shared cache of build artifacts
Clean the project.
Command group related to Coq.
Describe the workspace.
fetch and return errors from the current build
Execute a command in a similar environment as if installation was performed.
Removed command.
Format source code.
Format dune files
Additional Dune help
Command group for initializing dune components
Install packages.
Print out libraries installed on the system.

Start a merlin configuration server
Print the environment of a directory
Control how changes are propagated back to source code.
Dune's RPC mechanism. Experimental.
Dump internal rules.
Run tests.
cancel and shutdown any builds in the current workspace
Substitute watermarks in source files.
Print a list of toplevel directives for including directories and loading cma files.
Uninstall packages.
Upgrade jbuilder projects to dune
Load library in utop

These options are common to all commands.

--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.
--version
Show version information.

Use `dune COMMAND --help' for help on a single command.

dune exits with the following status:

0
on success.
123
on indiscriminate errors reported on standard error.
124
on command line parsing errors.
125
on unexpected internal errors (bugs).

These environment variables affect the execution of dune:

If different than 0, ANSI colors are supported and should be used when the program isn’t piped. If equal to 0, don’t output ANSI color escape codes
If different than 0, ANSI colors should be enabled no matter what.

Check bug reports at https://github.com/ocaml/dune/issues

1.
Initialise a new project named `foo':


dune init project foo
2.
Build all targets in the current source tree:


dune build
3.
Run the executable named `bar':


dune exec bar
4.
Run all tests in the current source tree:


dune runtest
5.
Install all components defined in the project:


dune install
6.
Remove all build artefacts:


dune clean
Dune n/a

Search for    or go to Top of page |  Section 1 |  Main Index

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with ManDoc.