> > > I wrote a tool to do this, but ran into the first problem above.
Perhaps I
> > > should investigate adding this capability to something like omake.
> >
> > Well ocamldep already does most of the work -- for Ocaml code.
>
> camldep does give all of the necessary information (well, it used to).  It
> seems to leave out dependencies that it thinks are obvious (foo.ml
produces
> foo.cmo or foo.cmx).  But, at least it has enough dependency information
to
> produce build rules.  I haven't seen anything actually use that
information
> though.

Ocamake is using ocamldep to build the dependency tree :
http://tech.motion-twin.com/ocamake.
However, two modules can be mutualy recursive from ocamldep point of view
(both ML depending on other MLI), and this is not enough information to know
in which order we need to link the CMO : this even might be impossible to
link in the cases the modules are effectively recursive ! OCamake is doing
some additional heuristics to try to guess which linking order is best.

Nicolas Cannasse

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners