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_mailing list <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] Re: what's in the future for ocamlbuild?
Date: Wed, 12 Mar 2008 16:11:37 +0100	[thread overview]
Message-ID: <1205334551-sup-608@port-ext16.ensta.fr> (raw)
In-Reply-To: <slrnftf8no.tll.sylvain@gallu.homelinux.org>

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

Excerpts from Sylvain Le Gall's message of Wed Mar 12 10:31:36 +0100 2008:
> Hello,
Hello,

> On 12-03-2008, Erick Tryzelaar <idadesub@users.sourceforge.net> wrote:
> >
> > - I love that ocamlbuild is bundled with ocaml as then it's one less
> > dependency for someone building an ocaml package, but I don't like how
> > it then ties it's release to ocaml releases. First, since new versions
> > of ocaml aren't really publicly planned, it's hard to know when a
> > feature might be added to ocamlbuild. Second, we can't use ocamlbuild
> > to build a system if the system compiler isn't 3.10. I don't think
> > ocamlbuild actually uses anything from 3.10. So, it would be nice if
> > there was also a separate release from ocaml that we could install
> > along side of an older ocaml install.
> >
> 
> Indeed, i would have prefer to have ocamlbuild outside ocaml compiler
> package. The reason for ocamlbuild in OCaml is to solve the complex
> scheme to build camlp4 (as far as i can remember). This is unfortunate,
> but we can't blame INRIA to build a tool and test it against its more
> complex compilation scheme.
> 
> > - A way for the community to add support for other languages. It may
> > not make sense to code in the OCaml tree support for things like Java
> > or the QT library. It also might not really be appropriate to be done
> > through OSR either.
> >
> > - ocamlbuild currently can't run on windows's cmd.exe, which is a
> > shame. This bug report suggests that it's not planned on changing
> > either:
> >
> > http://caml.inria.fr/mantis/view.php?id=4388
> >
> 
> I don't think INRIA team are against accepting your patches, if it fits
> correctly in OCaml. Most of the time, the first step is to provide a
> patch... If you have the time to correct this problem on your own, i
> think INRIA team will happily integrate your patch.

Talking  for  my parts (camlp4 and ocamlbuild), patches are welcome. Of course
they  are  subject  to  be  rejected  if  they  don't  fits  our  requirements
(including that INRIA is the copyright holder).

-- 
Nicolas Pouillard aka Ertai

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

  parent reply	other threads:[~2008-03-12 15:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-12  4:57 Erick Tryzelaar
2008-03-12  9:14 ` [Caml-list] " David Allsopp
2008-03-12 15:08   ` Nicolas Pouillard
2008-03-12 17:16   ` Erick Tryzelaar
2008-03-12  9:31 ` Sylvain Le Gall
2008-03-12 11:59   ` [Caml-list] " Lionel Elie Mamane
2008-03-12 12:05     ` Vincent Hanquez
2008-03-12 14:22       ` Sylvain Le Gall
2008-03-12 14:38         ` [Caml-list] " Vincent Hanquez
2008-03-12 14:52           ` Martin Jambon
2008-03-12 15:14           ` Sylvain Le Gall
2008-03-12 15:11   ` Nicolas Pouillard [this message]
2008-03-12 15:24 ` [Caml-list] " Nicolas Pouillard
2008-03-12 17:06   ` Erick Tryzelaar

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=1205334551-sup-608@port-ext16.ensta.fr \
    --to=nicolas.pouillard@gmail.com \
    --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