Gabriel Scherer

@kkirstein if you were interested in getting some of this patch merged, I think that would be very nice! There are some parts that were not intended for upstreaming (they...

Note: another route for you would be of course to submit an ocamlbuild.14.1 package in opam-repository-mingw, with the same patch as before (I would guess that the rebase would be...

Right now `ocamlbuild` is in maintenance-mode only, with no new developments planned, and the idea is to encourage people to migrate to `dune`. We keep the lights on and write...

@elfring would you like to send a pull request?

I gave an opinion on this mid-2018 in https://github.com/ocaml/ocamlbuild/pull/279#issuecomment-392315358 ; the fundamental reason why ocamlbuild insists on relative paths is that a path given by the user may be reinterpreted...

I don't really understand what the intended semantics is: if we copy the produced target to the source directory then, sure, ocamlbuild will copy it to _build instead of rebuilding...

Sounds amusing and potentially useful to have this capability, but there are two points that I would like clarification on: - Why must we lose the ability to bootstrap (build...

Small ping. @dra27, do you think that just keeping the ocamlbuild-specific *.ml* files in-repo would allow the bootstrap to keep working?

I'm preparing another ocamlbuild release today, and looking at this issue again. My conclusion is the same: why not use Dune as ocamlbuild build system, but I really would like...

Apologies for not clarifying this earlier. My actual workflow is rather like like ``` make all allopt cd bootstrap OCAMLBUILD="../ocamlbuild.native" make ``` in particular, installing is not required. (This impression...