caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Guillaume Rousse <Guillaume.Rousse@inria.fr>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] ocaml support in autotools
Date: Wed, 02 Aug 2006 14:46:53 +0200	[thread overview]
Message-ID: <44D09EBD.9010605@inria.fr> (raw)
In-Reply-To: <054b459f8307f928df4660099b19d65f@vistabella.de>

Christian Lindig wrote:
> 
> On Aug 1, 2006, at 10:15 AM, Erik de Castro Lopo wrote:
>> I'd like to have ocaml support in autotools (autoconf + automake),
> 
> Having a ./configure is very convenient for developers and users alike.
> Hoever, it does not have to be generated from Autoconf. The OCaml
> distribution uses manually written shell scripts, I am using a Perl
> script (since Perl is basically always available). You can take a look
> here:
> 
>     https://trac.vistabella.de/ocamlburg/browser/trunk/configure
> 
> I found it much easier to implement the checks that I need in my own
> little Perl script rather than relying on Autotools.
You're perfectly right, after all only the result really matters from a
user point of view.

However, from my own experience, people attempting to implement by
themselves a build system, instead of using/contributing to an existing
one (autotools is the not the only one) generally only consider their
own constraints, or the one they are aware of, and generaly fails in
specific scenarios, most notably packaging (properly tagged dynamic
librairies, parallel build, cross-compilation, specific optimisation
flags, fake root installation, etc...). Your own private wheel may be
more convenient for you, but it is generally less robust than one
routinely used by hundreds of people.

Of course, this is recurrente debate :)
-- 
Guillaume Rousse
Projet Estime, INRIA
Domaine de Voluceau
Rocquencourt - B.P. 105
78153 Le Chesnay Cedex - France


  parent reply	other threads:[~2006-08-02 12:46 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-31 16:14 Guillaume Rousse
2006-08-01  8:03 ` [Caml-list] " Stefano Zacchiroli
2006-08-01  8:15 ` Erik de Castro Lopo
2006-08-01  8:30   ` Christian Lindig
2006-08-01  8:51     ` Erik de Castro Lopo
2006-08-01 11:30     ` Hendrik Tews
2006-08-01 12:32       ` skaller
2006-08-01 12:50         ` Guillaume Rousse
2006-08-01 13:13           ` skaller
2006-08-02 12:46     ` Guillaume Rousse [this message]
2006-08-02 14:03       ` Christian Lindig
2006-08-01 11:27 ` Hendrik Tews
2006-08-01 11:51   ` Erik de Castro Lopo
2006-08-02 12:28   ` Guillaume Rousse
2006-08-01 17:37 ` Grigory Batalov
2006-08-02 12:29   ` [Caml-list] " Guillaume Rousse
     [not found] ` <44CE6483.9070205@tepkom.ru>
2006-08-03 12:56   ` [Caml-list] " Guillaume Rousse
2006-08-03 21:10     ` Erik de Castro Lopo
2006-08-04  0:40     ` Grigory Batalov
2006-08-04  5:32       ` [Caml-list] " skaller
2006-08-04  5:41         ` skaller
2006-08-04 12:38           ` Guillaume Rousse
2006-08-04  8:41         ` Anil Madhavapeddy
2006-09-08 14:52           ` Guillaume Rousse
2006-08-04 12:48         ` Stefano Zacchiroli
2006-08-05  0:36           ` skaller
2006-08-06  9:22             ` Stefano Zacchiroli
2006-09-08 14:52         ` Guillaume Rousse
2006-08-03 15:10   ` [Caml-list] " Guillaume Rousse
2006-08-03 21:12     ` Erik de Castro Lopo
2006-08-04 12:26       ` Guillaume Rousse
2006-08-04  1:15     ` Grigory Batalov
2006-08-03 22:42 ` [Caml-list] " Sylvain Le Gall

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=44D09EBD.9010605@inria.fr \
    --to=guillaume.rousse@inria.fr \
    --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;
as well as URLs for NNTP newsgroup(s).