Closed sheijk closed 3 years ago
Thanks for the suggestion. I think this is out of the scope of this project, mostly because it serves my needs and I'm not interested in managing a growing project.
You mention ocamldoc -dot
, which I haven't tried. There's also ocamldot
which processes the output of ocamldep
, which I used a long time ago. It was fun but not very useful because it was too messy and didn't really do anything to document a project. It would be good to know how to run ocamldep on a code base. In https://github.com/mjambon/dune-deps/issues/4, @jeremiedimino suggested looking into dune describe
. Maybe that would be appropriate for the task. That's all I know :-)
It would be great to have an option include modules in the graph instead of only having libraries and executables etc.
For example for the following dune file (repo)
I'm getting this output:
I'd like to be able to see all the modules (similar to the output of ocamldoc -dot).