From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.3 required=5.0 tests=AWL autolearn=disabled version=3.1.3 Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by yquem.inria.fr (Postfix) with ESMTP id 4BE87BBC1 for ; Wed, 12 Mar 2008 10:31:51 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AsAAAEo/10dQW+UCn2dsb2JhbACQcwEBAQEBBgQGCQgYmCE X-IronPort-AV: E=Sophos;i="4.25,486,1199660400"; d="scan'208";a="10166491" Received: from concorde.inria.fr ([192.93.2.39]) by mail3-smtp-sop.national.inria.fr with ESMTP; 12 Mar 2008 10:31:50 +0100 Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by concorde.inria.fr (8.13.6/8.13.6) with ESMTP id m2C9Vo9j000542 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=OK) for ; Wed, 12 Mar 2008 10:31:50 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AsAAAEo/10dQW+UCn2dsb2JhbACQcwEBAQEBBgQGCQgYmCE X-IronPort-AV: E=Sophos;i="4.25,486,1199660400"; d="scan'208";a="10166490" Received: from main.gmane.org (HELO ciao.gmane.org) ([80.91.229.2]) by mail3-smtp-sop.national.inria.fr with ESMTP; 12 Mar 2008 10:31:49 +0100 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JZNJG-0004jl-Mk for caml-list@inria.fr; Wed, 12 Mar 2008 09:31:42 +0000 Received: from ks300734.kimsufi.com ([91.121.65.225]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 12 Mar 2008 09:31:42 +0000 Received: from sylvain by ks300734.kimsufi.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 12 Mar 2008 09:31:42 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: caml-list@inria.fr From: Sylvain Le Gall Subject: Re: what's in the future for ocamlbuild? Date: Wed, 12 Mar 2008 09:31:36 +0000 (UTC) Message-ID: References: <1ef034530803112157m3bb804f4w6723252a84c2ec62@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: ks300734.kimsufi.com User-Agent: slrn/0.9.8.1pl2 (Debian) Sender: news X-Miltered: at concorde with ID 47D7A306.000 by Joe's j-chkmail (http://j-chkmail . ensmp . fr)! X-Spam: no; 0.00; le-gall:01 ocaml:01 ocaml:01 compiler:01 compiler:01 camlp:01 compilation:01 bug:01 sourceforge:01 wrote:01 dependency:01 caml:02 tree:02 patches:03 languages:03 Hello, On 12-03-2008, Erick Tryzelaar 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. Regards, Sylvain Le Gall