caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Grigory Batalov <bga@tepkom.ru>
To: caml-list@inria.fr
Subject: Re: ocaml support in autotools
Date: Tue, 1 Aug 2006 21:37:06 +0400	[thread overview]
Message-ID: <20060801213706.046ba31a.bga@tepkom.ru> (raw)
In-Reply-To: <44CE2C74.4070607@inria.fr>

On Mon, 31 Jul 2006 18:14:44 +0200
Guillaume Rousse <Guillaume.Rousse@inria.fr> wrote:

> I'd like to have ocaml support in autotools (autoconf + automake), to
> avoid heavy code duplication between several projects (at least
> ocmalimages and activedvi).
> 
> Autoconf support is quite simple to do, and even already done (I easily
> found  reference to
> http://www.lri.fr/~filliatr/ftp/ocaml/misc/configure.in.

  We have some modified scripts here too:
  http://oops.tepkom.ru/projects/template/
  There is also a short usage description.

> But instead of
> loosely distributing those macros in a custom package, as currently done
> in Debian,

  Which Debian package? (autoconf ?)

> I'd like to submit them directly to autoconf maintainers
> (with some modification, and with author's agreement of course). They
> are OK for this, provided there is some prior consensus in ocaml
> community first, to avoid continual macro change request of course.
> 
> Automake support is more complex, but apparently someone already tried
> it, as discussed at
> http://caml.inria.fr/pub/ml-archives/caml-list/2003/12/c9bf9f5d4423a9259f12ccc805fe4c1d.fr.html
> http://sourceware.org/ml/automake/2003-12/msg00153.html
> I'd be interested in current status of this effort before further
> investigation.


  parent reply	other threads:[~2006-08-01 17:40 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
2006-08-01 11:51   ` Erik de Castro Lopo
2006-08-02 12:28   ` Guillaume Rousse
2006-08-01 17:37 ` Grigory Batalov [this message]
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=20060801213706.046ba31a.bga@tepkom.ru \
    --to=bga@tepkom.ru \
    --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).