From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: OCaml List <caml-list@yquem.inria.fr>
Subject: Re: ocamlbuild documentation (was Re: [Caml-list] Re: [ANN] OCaml Batteries Included, alpha 3)
Date: Mon, 9 Feb 2009 15:37:21 +0100 [thread overview]
Message-ID: <3F6E6CB5-4609-49CE-BCFB-AD609B4BDD78@erratique.ch> (raw)
In-Reply-To: <499037FA.1090603@lri.fr>
Le 9 févr. 09 à 15:04, Romain Bardou a écrit :
> However, there ARE some examples in the part which talks about
> "flag", where we clearly see an usage (After_rules).
Which doesn't mean it cannot be used differently.
Anyway it seems useless arguing further: we just don't have the same
standards.
The only thing I see is that there are still a lot of mentions to
makefiles on this list and a lot of new projects don't use ocamlbuild
while ocamlbuild is clearly a superior alternative. The only way I can
explain this is by lack of good documentation. If you get the standard
distribution you don't get documentation for ocamlbuild (except a
brief manpage), there's no chapter on ocambuild in the manual, caml's
site documentation page doesn't even have a link to the small manual
or the wiki (you'll have to google to find it), the plugin api
documentation is not installed etc. etc.
It's a pitty, given its caml only implementation, ocamlbuild could
become a key part of a solid cross platform infrastructure for ocaml.
Alas it doesn't seem to be used much (and the reason is IMHO the sad
state of its documentation/advertising).
Best,
Daniel
next prev parent reply other threads:[~2009-02-09 14:38 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 16:11 [ANN] OCaml Batteries Included, alpha 3 David Rajchenbach-Teller
2009-02-07 14:21 ` [Caml-list] " Mikkel Fahnøe Jørgensen
2009-02-07 14:43 ` Sylvain Le Gall
2009-02-07 14:58 ` [Caml-list] " Jon Harrop
2009-02-07 15:13 ` Sylvain Le Gall
2009-02-07 16:13 ` [Caml-list] " Matthieu Dubuget
2009-02-07 19:30 ` David Rajchenbach-Teller
2009-02-07 21:13 ` Matthieu Dubuget
2009-02-09 9:36 ` Romain Bardou
2009-02-09 15:56 ` David Teller
2009-02-07 15:46 ` Paolo Donadeo
2009-02-09 9:32 ` Romain Bardou
2009-02-09 10:30 ` ocamlbuild documentation (was Re: [Caml-list] Re: [ANN] OCaml Batteries Included, alpha 3) Daniel Bünzli
2009-02-09 11:51 ` Romain Bardou
2009-02-09 12:30 ` Daniel Bünzli
2009-02-09 12:52 ` Romain Bardou
2009-02-09 13:07 ` Daniel Bünzli
2009-02-09 13:22 ` Romain Bardou
2009-02-09 13:36 ` Daniel Bünzli
2009-02-09 13:59 ` Romain Bardou
2009-02-09 14:04 ` Romain Bardou
2009-02-09 14:37 ` Daniel Bünzli [this message]
2009-02-09 17:26 ` Kuba Ober
2009-02-09 18:28 ` Jon Harrop
2009-02-09 21:24 ` DooMeeR
2009-02-10 14:06 ` ocamlbuild documentation Jan Kybic
2009-02-10 14:27 ` [Caml-list] " Matthieu Dubuget
[not found] ` <87k57ywc0k.fsf@fel.cvut.cz>
2009-02-10 15:50 ` Matthieu Dubuget
2009-02-10 15:58 ` Daniel Bünzli
2009-02-09 18:38 ` ocamlbuild documentation (was Re: [Caml-list] Re: [ANN] OCaml Batteries Included, alpha 3) David Teller
2009-02-09 22:02 ` [Caml-list] Re: [ANN] OCaml Batteries Included, alpha 3 Peter Hawkins
2009-02-09 22:45 ` Mikkel Fahnøe Jørgensen
2009-02-09 22:55 ` Mikkel Fahnøe Jørgensen
2009-02-10 7:48 ` Stefano Zacchiroli
2009-02-10 13:22 ` Mikkel Fahnøe Jørgensen
2009-02-07 20:04 ` Daniel Bünzli
2009-02-08 17:22 ` [Caml-list] " Richard Jones
2009-02-09 8:57 ` David Allsopp
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=3F6E6CB5-4609-49CE-BCFB-AD609B4BDD78@erratique.ch \
--to=daniel.buenzli@erratique.ch \
--cc=caml-list@yquem.inria.fr \
/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