> * A wiki is not documentation. The reference document that documents the
> conceptual model of ocamlbuild, the available tags and their effects
> and a clear/understandable documentation of the *API* are still
> missing. How does ocamlbuild build your project, how does it compute
> dependencies, how does it track changes, etc.
I agree we have to think, how to build up to date documentation as our
top priority. Embarrassingly it's been on my plate for quite long. Now I
think time is up, to update it.
> API is the right one or if it's just a matter of the missing
> documentation. And this is from a person who has written significant
> current strategy is to switch to a mixture of shell scripts and
> * Easy built-in support for C stubs/libraries is missing. E.g. I'd be
> like this [3].
The trouble is that OCamlbuild itself is really a build framework. It
contains a lot of rules out of the box, though, but they usually all
related to ocaml system, and not the external tools. Because we have no
method of distributing various plugins for OCamlbuild (Coq rules,
Js_of_ocaml rules, C rules, LaTeX rules etc.) it means that every
project hacks it own plugin, perhaps by copy pasting from the wiki. This is
un-satisfactory and a real root of the problem. Fortunately the solution
for this exist, we should allow ocamlfind packages to install needed
rules. We could say then:
ocamlbuild -use_package js_of_ocaml.ocamlbuild
Wojciech