I usually always forgot the commands on generating documentation, and how to run the executable. I go through a series of
dune exec to
dune exec <name> to
dune exec <name>.exe, finally to remember its
dune exec ./bin/<name>.exe. Same with
dune test, which is really
An issue I have with dune’s documentation is it’s just way too large. To quote Jerry Seinfeld,
Did you see the size of that thing? It’s like the Declaration of Independence. No one is going to read that
I just want to know the bear minimum commands to build/run/publish my project. So writing it all down once in a Makefile with easy names, and generating it for new projects makes it so much simpler for me.
As for generating the opam file with dune. That’s an interesting idea that I forgot dune was capable of. I’ll definitely look into that. Thanks!