Hi,
There is no explicit install step. You’d want to add ppx_deriving to your dune-project file, then call dune pkg lock
(which dune tells you to do IIRC), and the next build will download/build any new dependencies. Doc: Managing Dependencies - Dune documentation.
dune install
is not comparable to opam install
, I guess its functionality and name is taken from the make install
convention.
You can add [@@@ocaml.warnerror "-34-69"]
at the top of your file. The problem with warnings-as-not-errors is that warnings will only be given when the file is compiled. So if you run dune build && dune build
, the second build will never report any warning.
The tutorial should explain how to setup dev tools, but since it doesn’t, I think this post is the only written explanation.