[opam-devel] opam/ocp-index integration guidelines

[Louis Gesbert]

Le mercredi 18 décembre 2013, 13:31:24 Daniel Bünzli a écrit :
> Ok so if I gather well:
> 
> 1) Installing a .cmi is enough for completion and getting the type. 
> 2) Installing .cmti adds the (ocaml)docs of each function (which is nice).

Yup. Additionally, the .cmt may be used if the cmti is absent, when specified on the command-line (done on the currently open file by emacs), or when looking up the implementation location.

> 
> However:
> > (I think ocp-index looks for any _build or _obuild parent subdir to find the cmt of the current project and in all `opam config var lib` subdirs for the installed packages).
> This assertion seems to be wrong:
> 
> > ocp-index complete Tsdl.Sdl.init
> 
> 
> 
> returns nothing. While:
> 
> > ocp-index complete -I `opam config var tsdl:lib` Tsdl.Sdl.init
> Tsdl.Sdl.init val Init.t -> unit result
> 
> Tsdl.Sdl.init_sub_system val Init.t -> unit result
> 
> Should I file a bug report with ocp-index ? 
> 
> Best,
> 
> Daniel
> _______________________________________________
> opam-devel mailing list
> opam-devel at lists.ocaml.org
> http://lists.ocaml.org/listinfo/opam-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ocaml.org/pipermail/opam-devel/attachments/20131223/4e58dbdb/attachment.html>