Ashish Agarwal

b1e88b9f9e0d20f28e9eada4d8cac281de29c860 adds support for `-strict-sequence`.

I'm uncertain which directory to give to the CMT directives. The link you provided implies that you _have to_ tell opam to keep the build directory, but I find plenty...

Adding `-no-hygiene` could be fine. Would you mind testing in your environment and see if it firstly resolves this issue, and second that some other unexpected thing doesn't happen. As...

Hmm... so is `-no-hygiene` the culprit? Is there some way to tell ocamlbuild `-no-traverse`, other than creating an `_tags` file?

We should be able to handle this by adding `Ocamlbuild_plugin.tag_any ["-traverse"]` to our plugin definitions, which effectively does "true: -traverse". However, it doesn't work. I tried adding it to `Before_hygiene`...

6b8d6122ee75f9ce29ac23d3ae53d0d6e7da9c89 improves the situation. I tested on several projects, and this seems to work but there's still one issue: The cmo files seem to get built in the order they...

Commit 064d8e08e3e8c379936fbdfdc4ba9f07fa2d59b5 possibly resolves this issue, at least in terms of correctness. However, the solution is not efficient. As the commit message says, I've now prohibited parallel builds for all...

> it still permits a correct (only suboptimal) compilation Right. I guess the `.cmi` gets regenerated when it is not strictly necessary to do so. I haven't tested the affect...

Here's a test case: ``` $ cat myocamlbuild.ml open Ocamlbuild_plugin let () = dispatch (function | Before_options -> ( Options.use_ocamlfind := true ;Ocamlbuild_pack.Configuration.parse_string ": foo" ) | _ -> ()...

Ignore last question. I was doing something else wrong. Here's a solution that is working so far: - Copy contents of your `_tags` file into an OCaml variable in `myocamlbuild`,...