diff options
| author | Théo Zimmermann | 2018-09-05 13:04:00 +0200 |
|---|---|---|
| committer | Théo Zimmermann | 2018-09-05 13:04:00 +0200 |
| commit | 579f30a53809f9cf73aa3d7c69960b50fc51c7fc (patch) | |
| tree | da69bfd576092da56f66c04ae800db5ae0042c33 /dev/doc/build-system.dev.txt | |
| parent | dc78205a55fe1825c8744d3acb7bb43e08d39c4e (diff) | |
| parent | 920723ab4c1707c0a98c978cdd7742d47e58582f (diff) | |
Merge PR #6857: [build] Preliminary support for building with `dune`.
Diffstat (limited to 'dev/doc/build-system.dev.txt')
| -rw-r--r-- | dev/doc/build-system.dev.txt | 40 |
1 files changed, 33 insertions, 7 deletions
diff --git a/dev/doc/build-system.dev.txt b/dev/doc/build-system.dev.txt index abba13428f..b0a2b04121 100644 --- a/dev/doc/build-system.dev.txt +++ b/dev/doc/build-system.dev.txt @@ -1,5 +1,3 @@ - - HISTORY: ------- @@ -35,13 +33,41 @@ HISTORY: grammar.cma (and q_constr.cmo) directly, no need for a separate subcall to make nor awkward include-failed-and-retry. - ---------------------------------------------------------------------------- +* February - September 2018 (Emilio Jesús Gallego Arias) + + Dune support added. + + The build setup is mostly vanilla for the OCaml part, however the + `.v` to `.vo` compilation relies on `coq_dune` a `coqdep` wrapper + that will generate the necessary `dune` files. + + As a developer, you should not have to deal with Dune configuration + files on a regular basis unless adding a new library or plugin. + The vanilla setup declares all the Coq libraries and binaries [we + must respect proper containment/module implementation rules as to + allow packing], and we build custom preprocessors (based on `camlp5` + and `coqpp`) that will process the `ml4`/`mlg` files. + + This suffices to build `coqtop` and `coqide`, all that remains to + handle is `.vo` compilation. + + To teach Dune about the `.vo`, we use a small utility `coq_dune`, + that will generate a `dune` file for each directory in `plugins` and + `theories`. The code is pretty straightforward and declares build + and install rules for each `.v` straight out of `coqdep`. Thus, our + build strategy looks like this: + + 1. Use `dune` to build `coqdep` and `coq_dune`. + 2. Use `coq_dune` to generate `dune` files for each directory with `.v` files. + 3. ? + 4. Profit! [Seriously, at this point Dune has all the information to build Coq] + +--------------------------------------------------------------------------- -This file documents internals of the implementation of the build -system. For what a Coq developer needs to know about the build system, -see build-system.txt . +This file documents internals of the implementation of the make-based +build system. For what a Coq developer needs to know about the build +system, see build-system.txt and build-system.dune.md . .ml4 files ---------- |
