From: "David Allsopp" <dra-news@metastack.com>
To: "'Richard Jones'" <rich@annexia.org>,
"'Mikkel Fahnøe Jørgensen'" <mikkel@dvide.com>
Cc: "'David Rajchenbach-Teller'" <David.Teller@ens-lyon.org>,
"'OCaml'" <caml-list@inria.fr>
Subject: RE: [Caml-list] [ANN] OCaml Batteries Included, alpha 3
Date: Mon, 9 Feb 2009 08:57:51 -0000 [thread overview]
Message-ID: <006401c98a94$7e2f45f0$7a8dd1d0$@com> (raw)
In-Reply-To: <20090208172223.GB31948@annexia.org>
On Sun, Feb 08, 2009 Richard Jones wrote:
> For example, everyone loves to hate autoconf (me included), but in
> actual fact you only have to write two files containing under 10 lines
> of code in each, to make a complete build environment for an OCaml
> program under autotools. This fact probably isn't obvious, because
> nowhere is it documented.
+1! And projects like GnuWin32[1] mean that it doesn't take too much extra
work to support Windows builds within the same build framework.
> Similarly, plain Makefiles are easy to do, including working
> dependencies. Just needs to be documented.
Would a line-by-line analysis of something comprehensive like OCamlMakefile
be a good example for anyone wishing to see how OCaml building is expressed
in make (I'm afraid I don't use it so can't really volunteer to do that - I
get everything I need for writing Makefiles from the GNU info pages and
O'Reilly's excellent "Managing projects with make" book)
David
[1] http://gnuwin32.sourceforge.net
prev parent reply other threads:[~2009-02-09 8:58 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 16:11 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
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 [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='006401c98a94$7e2f45f0$7a8dd1d0$@com' \
--to=dra-news@metastack.com \
--cc=David.Teller@ens-lyon.org \
--cc=caml-list@inria.fr \
--cc=mikkel@dvide.com \
--cc=rich@annexia.org \
/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;
as well as URLs for NNTP newsgroup(s).