A composable build system for OCaml.
Branch: master
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Add @emillon as codeowner for catapult Dec 14, 2018
bench Use shorter library names to shorten internal paths used by Dune Feb 5, 2019
bin Fix dune subst not setting build root Feb 18, 2019
doc Add c_flags to env profile settings Feb 22, 2019
editor-integration/emacs Emacs: quote filename before passing it to a shell command Feb 6, 2019
example Update tests Jan 8, 2019
plugin Forbid #require in dune files in OCaml syntax (#938) Jul 2, 2018
src ocp-indent Super_context Feb 22, 2019
test Rewrite printenv.sh into cram Feb 22, 2019
vendor Upgrade cmdliner Dec 14, 2018
.gitignore Update .gitignore bootstrap dir Feb 5, 2019
.ocp-indent Add a .ocp-indent file Mar 4, 2017
.travis-ci.sh Remove wrong dune version from CI Feb 22, 2019
.travis.yml Add 4.04 & 4.05 to test matrix Feb 5, 2019
CHANGES.md Update CHANGES wrt 1.7.2 Feb 22, 2019
CONTRIBUTING.md [doc] Add coding style to CONTRIBUTING. (#1640) Dec 14, 2018
HACKING.md documentation fixes Feb 4, 2019
LICENSE.md Switch to MIT License May 23, 2018
MIGRATION.md Refer to migration page from manual and readme Jun 25, 2018
Makefile _build_bootstrap --> _boot Feb 5, 2019
README.md _build_bootstrap --> _boot Feb 5, 2019
appveyor.yml _build_bootstrap --> _boot Feb 5, 2019
bootstrap.ml Use shorter library names to shorten internal paths used by Dune Feb 5, 2019
configure Allow to set the library path at configure time (#575) Mar 6, 2018
configure.ml Allow to set the library path at configure time (#575) Mar 6, 2018
dune-project Do not remove parentheses in inferred rules Jan 15, 2019
dune-workspace.dev Update workspace file for 4.07.0 Jul 15, 2018
dune.opam Add base-unix and base-threads dependencies (#1564) Nov 22, 2018
install_ocaml.cmd Update AppVeyor to OCaml 4.06.0 Nov 15, 2017

README.md

Dune - A composable build system

Dune is a build system designed for OCaml/Reason 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.

Dune comes with a manual. If you want to get started without reading too much, you can look at the quick start guide or watch this introduction video.

The example directory contains examples of projects using dune.

Travis status AppVeyor status

Overview

Dune reads project metadata from dune files, which are either static files in a simple S-expression syntax or OCaml scripts. It uses this information to setup build rules, generate configuration files for development tools such as merlin, handle installation, etc...

Dune itself is fast, has very low overhead and supports parallel builds on all platforms. It has no system dependencies: all you need to build dune and packages using dune is OCaml. You don't need make or bash as long as the packages themselves don't use bash explicitly.

Especially, one can install OCaml on Windows with a binary installer and then use only the Windows Console to build dune and packages using dune.

Strengths

Composable

Take n repositories that use dune, arrange them in any way on the file system and the result is still a single repository that dune knows how to build at once.

This make simultaneous development on multiple packages trivial.

Gracefully handles multi-package repositories

Dune knows how to handle repositories containing several packages. When building via opam, it is able to correctly use libraries that were previously installed even if they are already present in the source tree.

The magic invocation is:

$ dune build --only-packages <package-name> @install

Building against several configurations at once

Dune is able to build a given source code repository against several configurations simultaneously. This helps maintaining packages across several versions of OCaml as you can test them all at once without hassle.

In particular, this makes it easy to handle cross-compilation.

This feature requires opam.

Requirements

Dune requires OCaml version 4.02.3 or greater.

Installation

The recommended way to install dune is via the opam package manager:

$ opam install dune

You can also build it manually with:

$ make release
$ make install

Running simply make will build dune using the development settings.

If you do not have make, you can do the following:

$ ocaml bootstrap.ml
$ ./boot.exe
$ ./_boot/default/bin/main_dune.exe install dune

Support

If you have questions about dune, you can send an email to ocaml-core@googlegroups.com or open a ticket on github.

Migration from jbuilder

Dune was formerly known as jbuilder. Migration from jbuilder to dune is described in the manual.

Status

Dune is now fairly stable and is used by the majority of packages on opam. Note that dune retains backward compatibility with Jbuilder, and in particular existing Jbuilder projects will continue to be buildable with dune.