Gabriel Scherer

What I understand from your experiments is that my worries are moot because any use of backslash (be it part of the path, or an attempt to escape spaces) is...

I agree that quoted strings are fine. @jonahbeckford I think that I got us in the wrong direction with my previous question on non-Windows peoples using spaces or backslashes in...

Ah, good point about dependencies being available at package-configure-time already. > The only annoying bit seems to be the `include $(shell ocamlc -where)/Makefile.config` We can call `ocamlc -config` from within...

I'd like to thank everyone involved here for the end result which is a net improvement to the upstream ocamlbuild windows story (stories, as several distinct configurations are in use)....

@Armael, are you looking for a weekend ocamlbuild contribution thrill?

You report the following behavior on the dune issue: ``` $ _build/_private/default/.pkg/ocamlbuild/target/bin/ocamlbuild -where /home/s/tmp/bonsai/_build/.sandbox/7158a9da761d39477e414a6f2dd9d3fc/_private/default/.pkg/ocamlbuild/target/lib/ocamlbuild ``` Two comments: 1. The standard way to deal with this issue in Linux distributions is...

> The path variables such as bin and lib are set within the sandbox where the build is performed rather than within the destination filesystem but perhaps that is something...

So the actionable content of this issue is "we should fix the rendering of `.mli` documentation". Once we do this, and get a public link to the API documentation somewhere...

I'm looking at this in more detail. Currently a raw `ocamldoc *.mli -html` produces output that is not very nice, because it merely gives a haphazard list of modules, some...

#227 installs `signature.{cmi,cmti}`. There is one thing I find surprising: the current Makefile is already careful to install `signatures.mli`, so why is the Signatures module not visible in the odig-generated...