Re: [Caml-list] Development status of the dependency generator for OCaml

[SF Markus Elfring <elfring@users.sourceforge.net>]

> It surprises me to find that ocamldep -all foo.mli doesn't generate `foo.cmi: foo.mli`, …

Thanks for your acknowledgement.


> What are you regarding as erroneous about the entries with 
> "only a dependency on a single compiled module interface"
> (for bytecode, that sounds correct to me).

A software build system which can support the programming language “OCaml”
to some some degree will contain generation rules for involved file types
as you mentioned it also.


> You mean that you'd like simple cases eliminated?

Yes. - The provided data set should eventually not repeat specifications
for dependencies for which you care by the selected build system already.


> foo.cmi:
> foo.cmo: foo.cmi
> 
> should simply not be printed, and be assumed to work with implicit rules?

Yes. - In principle for the default data export variant.

I looked into a few OCaml build configurations where the desired dependency
handling seems to work better with explicit make rules and corresponding
automatic rule generation.

Regards,
Markus