Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: "Nicolas Pouillard" <nicolas.pouillard@gmail.com>
To: caml-list <caml-list@inria.fr>
Cc: "daniel.buenzli" <daniel.buenzli@erratique.ch>
Subject: Re: [Caml-list] build, distribution, data and metadata
Date: Sat, 02 Feb 2008 12:10:12 +0100	[thread overview]
Message-ID: <1201950423-sup-7278@ausone.local> (raw)
In-Reply-To: <47A3A390.7080308@metaprl.org>

[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]

Excerpts from nogin's message of Fri Feb 01 23:56:16 +0100 2008:
> On 29.01.2008 09:56, Bünzli Daniel wrote:
> 
> >>   I know there is Omake,
> > 
> > Having used ocamlbuild for caml projects, for me it is out of question
> > to return to something make-like.
> 
> On 31.01.2008 01:28, Nicolas Pouillard wrote:
> 
> >> - the make files are written in a well defined language
> > Considering GNU make, BSD make, pmake, bmake, omake... I would say no.
> 
> IMHO it would be improper to consider OMake as being make-like and group
> it together with various make variants. While some very basic elements
> of OMake syntax are made to resemble make in order to facilitate
> learning OMake for those familiar with make, but in most respects it is
> a lot closer to, say, ocamlbuild than to make.

I  think  you're  right,  I  really  hesitated to put omake in the same group,
because that's really *not* just a make variant.

Of course being ocamlbuild-opinionated didn't helped me :)

-- 
Nicolas Pouillard aka Ertai

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 186 bytes --]

      reply	other threads:[~2008-02-02 11:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31  8:57 Cristian Baboi
2008-01-31  9:28 ` [Caml-list] " Nicolas Pouillard
2008-01-31  9:55   ` Cristian Baboi
2008-02-01 22:56   ` Aleksey Nogin
2008-02-02 11:10     ` 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=1201950423-sup-7278@ausone.local \
    --to=nicolas.pouillard@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=daniel.buenzli@erratique.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