From: Nicolas Pouillard <nicolas.pouillard@gmail.com>
To: Guillaume Yziquel <guillaume.yziquel@citycable.ch>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] ocamlbuild and ocamlfind - infer_interface
Date: Sat, 28 Feb 2009 21:40:26 +0100 [thread overview]
Message-ID: <1235853582-sup-1603@ausone.local> (raw)
In-Reply-To: <49A999CE.50503@citycable.ch>
Excerpts from Guillaume Yziquel's message of Sat Feb 28 21:08:46 +0100 2009:
> Hello.
>
> A small comment on the ocamlbuild wiki, and more specifically on its
> plugin for ocamlfind:
>
> http://brion.inria.fr/gallium/index.php/Using_ocamlfind_with_ocamlbuild
>
> This plugin fails to generate .inferred.mli files. The following lines
> (thanks to bluestorm on #ocaml irc channel) are needed in the
> After_rules of the plugin:
>
> -1- flag ["ocaml"; "infer_interface"; "pkg_"^pkg] & S[A"-package"; A pkg];
>
> -2- flag ["ocaml"; "infer_interface"; "syntax_"^syntax] & S[A"-syntax";
> A syntax];
>
> -3- flag ["ocaml"; "pkg_threads"; "infer_interface"] (S[A "-thread"])
>
> Since I could not find a single occurrence of "infer_interface" on the
> Gallium wiki, and since I do not believe that using ocamlbuild and
> ocamlfind together to infer .mli files is "not a simple task", I
> sincerely believe that the documentation of ocamlbuild is insufficient,
> and insufficently structured. (This is to echo the debate between Daniel
> Bünzli and Romain Bardou, among others, two or three weeks ago
> concerning the lack of documentation).
>
> Could these three lines be added to the myocamlbuild.ml plugin for
> ocamlfind on the Gallium wiki, and could tags such as "infer_interface"
> be documented thoroughly on the wiki? That would be helpful!
Thanks for this contribution.
I've added these 3 lines in the Wiki.
--
Nicolas Pouillard
prev parent reply other threads:[~2009-02-28 20:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-28 20:08 Guillaume Yziquel
2009-02-28 20:40 ` Nicolas Pouillard [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1235853582-sup-1603@ausone.local \
--to=nicolas.pouillard@gmail.com \
--cc=caml-list@inria.fr \
--cc=guillaume.yziquel@citycable.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox