From: Martin DeMello <martindemello@gmail.com>
To: Marek Kubica <marek@xivilization.net>
Cc: r.3@libertysurf.fr, "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] which ocaml build system
Date: Thu, 25 Jul 2013 14:45:02 -0700 [thread overview]
Message-ID: <CAFrFfuGD-gzfZx6Z44qo5z_3WQohvnJ8YuRU40w74Nkt-2fCjA@mail.gmail.com> (raw)
In-Reply-To: <20130723153956.605104b3@xivilization.net>
On Tue, Jul 23, 2013 at 6:39 AM, Marek Kubica <marek@xivilization.net> wrote:
>
>> I would like to gather thoughts on that in the ocaml.org website,
>> because actually its advice is 'make + OcamlMakefile' and 'Omake',
>> and I am not sure it is the best advice.
>
> I suppose this advice used to be good, but today maybe not as much
> anymore.
I have an old (and fairly small) project that I've tried at least
thrice to migrate off OcamlMakefile to something more
modern/ocaml-specific, and failed each time (after spending 1-2
evenings on it). I'll give it another go and report back on my
experience, but at least historically OCamlMakefile was the easiest
thing to get up and running.
You can see the pretty simple makefile here:
https://github.com/martindemello/varix/blob/master/makefile - I can't
remember exactly what difficulties I had with ocamlbuild and omake
now.
martin
next prev parent reply other threads:[~2013-07-25 21:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51ECF4EB.1060301@libertysurf.fr>
2013-07-22 9:07 ` r.3
2013-07-22 15:11 ` Ashish Agarwal
2013-07-23 13:39 ` Marek Kubica
2013-07-25 21:45 ` Martin DeMello [this message]
2013-07-26 1:10 ` Francois Berenger
2013-07-26 5:01 ` Malcolm Matalka
2013-07-26 5:46 ` Adrien Nader
2013-07-26 6:49 ` rixed
2013-07-26 7:07 ` David Allsopp
2013-07-26 4:49 ` Gabriel Scherer
2013-08-05 17:34 ` [Caml-list] character syntax error '^M' r.3
2013-08-05 17:38 ` David Allsopp
2013-08-05 20:23 ` William R
2013-08-06 10:52 ` David Allsopp
2013-07-27 9:51 ` [Caml-list] which ocaml build system Goswin von Brederlow
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=CAFrFfuGD-gzfZx6Z44qo5z_3WQohvnJ8YuRU40w74Nkt-2fCjA@mail.gmail.com \
--to=martindemello@gmail.com \
--cc=caml-list@inria.fr \
--cc=marek@xivilization.net \
--cc=r.3@libertysurf.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;
as well as URLs for NNTP newsgroup(s).