[Omake] More on ocamldep and generated files.

[malc]

On Mon, 12 Jun 2006, Aleksey Nogin wrote:

> After thinking some more about this, it seems to me that the problem
> lies in ocamldep trying to do two things:
>

[snip]

>
> So my proposal would be to:
> 1) Lobby OCaml maintainers to add a "-modules" flag that would cause
> ocamldep to forgo the second step, simply printing out the list of modules.

Like http://caml.inria.fr/mantis/view.php?id=3162 ?

>
> 2) Implement an _internal_ function that would use the output of the
> "ocamldep -modules" command to search for a _buildable_ target (using
> the full knowledge of the internal build state) in the OCAMLINCLUDES path.
>
> Note that a similar approach should work for all other languages as well!
>
> P.S. In order to be able to do step "2" efficiently, we might need to
> make some minor modifications to OMake, but this should not be a problem.

P.S. ocamldep works on purely syntactic level, hence errors in situation
      when an opened module contains submodule named Submod and submod.ml
      exists and is reachable. I doubt that nothing short of a scanner that
      understands ML module language will suffice to do the job _correctly_

--
mailto:malc at pulsesoft.com