Re: [Caml-list] Forcing OCamlbuild to compile a file before another

[Dario Teixeira <dario.teixeira@nleyten.com>]

Hi,

> I am not sure. But: why isn't the dependency explicit in
> lambwiki_parser.mly? Doesn't it mention the module name
> "Lambwiki" somewhere? If not, perhaps you could add a
> fake dependency by declaring "module L = LambWiki" at
> the top of lambwiki_parser.mly. Would that help?

I'm still poking at it, but it seems there may be a bug in OCamlbuild,
or at least a difference of opinion. (I am using module aliases and
-no-alias-deps, and some of these waters are uncharted).

In the tags file, I had declared a tag "open(Lambwiki)" for file
<lambwiki_parser.mly>.  I assumed this would automatically add a
dependency on lambwiki.ml for lambwiki_parser.mly.

Now, lambwiki.ml contains only module aliases, for instance:

module Parser = Lambwiki_parser
module Scanner = Lambwiki_scanner

To avoid a circular dependency, in myocamlbuild I use the non_dependency
function (part of OCamlbuild's API) to declare that lambwiki.ml does not
in fact depend on Lambwiki_parser and Lambwiki_scanner.

I wonder if the tooling expects module aliases to produce dependencies
the other way around, ie, Lambwiki_parser depends on Lambwiki but not
vice-versa.  This is not clear to me.

Anyway, adding a dummy dependency as you suggested does the trick for
this particular problem.

Kind regards,
Dario Teixeira