caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Hendrik Tews <tews@cs.ru.nl>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] ocaml support in autotools
Date: 01 Aug 2006 13:27:16 +0200	[thread overview]
Message-ID: <wwuejw0u25n.fsf@tandem.cs.kun.nl> (raw)
In-Reply-To: <44CE2C74.4070607@inria.fr>

Guillaume Rousse <Guillaume.Rousse@inria.fr> writes:

   I'd like to have ocaml support in autotools (autoconf + automake), to
   avoid heavy code duplication between several projects (at least
   ocmalimages and activedvi).
   
I would very much like to see this. Please go ahead. I did some
autoconf hacking for the CCSL compiler, see the files aclocal.ml
and configure.ac in
http://wwwtcs.inf.tu-dresden.de/~tews/ccsl/viewcvs.cgi/Ccslc/
Feel free to reuse that code.

The main problem with autoconf from my point of view (at least in
2.57, the latest version I looked at) is that it provides a lot
of stuff, which is only relevant for C/C++ projects and which you
cannot easily disable. For instance the configure options
--includedir. Further, there is no way to add an additional
configure option. I have therefore overridden the internal macros
_AC_INIT_PARSE_ARGS and _AC_INIT_HELP in a private aclocal.m4.
However, now I have to adopt my changes to every new autoconf
version. Idially, there should be a simple way to disable each of
the standard configure options and to add new ones.

   http://www.lri.fr/~filliatr/ftp/ocaml/misc/configure.in

This version searches in the PATH, but sometimes the right ocaml
version is not in the path.

Bye,

Hendrik Tews


  parent reply	other threads:[~2006-08-01 11:27 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
2006-08-02 14:03       ` Christian Lindig
2006-08-01 11:27 ` Hendrik Tews [this message]
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=wwuejw0u25n.fsf@tandem.cs.kun.nl \
    --to=tews@cs.ru.nl \
    --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).