caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Goswin von Brederlow <goswin-v-b@web.de>
To: caml-list@inria.fr
Subject: Re: [Caml-list] which ocaml build system
Date: Sat, 27 Jul 2013 11:51:50 +0200	[thread overview]
Message-ID: <20130727095150.GB4948@frosties> (raw)
In-Reply-To: <CAFrFfuGD-gzfZx6Z44qo5z_3WQohvnJ8YuRU40w74Nkt-2fCjA@mail.gmail.com>

On Thu, Jul 25, 2013 at 02:45:02PM -0700, Martin DeMello wrote:
> 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

I vote for oasis. Its kind of a meta build system in that it then
generates you a Makefile, configure, setup.ml, myocamlbuild.ml (in my
case) and _tags to do the actual building.

It can build libraries, packed and not packed, binaries and test
suites with verry little input. It generates META files for libs and
handles build dependencies on other libs or libs from part of the same
source. The generated files can also be extended in case you need
something oasis doesn't know about. Never had the need for that yet.

MfG
	Goswin

      parent reply	other threads:[~2013-07-27  9:51 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
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       ` Goswin von Brederlow [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=20130727095150.GB4948@frosties \
    --to=goswin-v-b@web.de \
    --cc=caml-list@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;
as well as URLs for NNTP newsgroup(s).