Gabriel Scherer

Frankly, I don't know what should be done. These days (and in the recent past) I had zero time to work on ocamlbuild's performance, which are "good enough" for most...

An amusing problem! Daniel's idea to use symlinks seems reasonable, but we would need to double-check that ocamlbuild is fine with these files being modified behind its back. (For example...

(Also I find the idea of using `-no-hygiene` rather dubious, and I'm not even sure it would solve the problem. Would it prevent ocamlbuild from erasing `_build/foo.ml` when `foo.ml` has...

I'm not sure what would be a good way to avoid that. The `.mli` files that ocamldoc depends on are "built" by ocamlbuild, that is found and copied to the...

Yeah, I agree your idea sounds potentially better, and it could be useful in other situations. (For example if the source is taken from the web for some reason, you...

So it seems that the first priority would be to get `ocamldoc` to display relative instead of absolute file paths, to be consistent with the OCaml compiler (this is why...

Why not, indeed. That still does not prevent the problem of editing generated file (only copied source files), but maybe that is good enough?

I have a first patch up against ocamldoc. The change is rather blind-sighted, though; I cannot be fully sure it is correct, and this may delay integration.

We have done a first round of fixing, but I think that there is a larger usability issue at play here that should be taken seriously. ocamlbuild keeps a cache/log...

Storing color escape codes in the log should be fine as long as users use color-aware tools to read the log (eg. `less -R`). I just tried and `-tag "color(always)"`...