From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id AC8DF81799 for ; Fri, 26 Jul 2013 07:27:03 +0200 (CEST) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of berenger@riken.jp) identity=pra; client-ip=134.160.33.162; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="berenger@riken.jp"; x-sender="berenger@riken.jp"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of berenger@riken.jp designates 134.160.33.162 as permitted sender) identity=mailfrom; client-ip=134.160.33.162; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="berenger@riken.jp"; x-sender="berenger@riken.jp"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of postmaster@postman.riken.jp designates 134.160.33.162 as permitted sender) identity=helo; client-ip=134.160.33.162; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="berenger@riken.jp"; x-sender="postmaster@postman.riken.jp"; x-conformance=sidf_compatible; x-record-type="v=spf1" X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AtQBAMIH8lGGoCGinGdsb2JhbABagzy7OIJ9gSwOAQEBAQEICwkJFCiCJAEBBAEyAQU2CgYLCxgJFg8JAwIBAgFFEwgBAYgGBrkekAQWg2oDiSiON4Yjjk0 X-IPAS-Result: AtQBAMIH8lGGoCGinGdsb2JhbABagzy7OIJ9gSwOAQEBAQEICwkJFCiCJAEBBAEyAQU2CgYLCxgJFg8JAwIBAgFFEwgBAYgGBrkekAQWg2oDiSiON4Yjjk0 X-IronPort-AV: E=Sophos;i="4.89,748,1367964000"; d="scan'208";a="22303475" Received: from postman2.riken.jp (HELO postman.riken.jp) ([134.160.33.162]) by mail3-smtp-sop.national.inria.fr with ESMTP; 26 Jul 2013 07:27:02 +0200 Received: from postman.riken.jp (postman2.riken.jp [127.0.0.1]) by postman.riken.jp (Postfix) with SMTP id 03E531260520 for ; Fri, 26 Jul 2013 14:26:59 +0900 (JST) Received: from [172.27.98.103] (rikad98.riken.jp [134.160.214.98]) by postman.riken.jp (Postfix) with ESMTPA id BA9E81270051 for ; Fri, 26 Jul 2013 14:26:59 +0900 (JST) Message-ID: <51F2089D.4000104@riken.jp> Date: Fri, 26 Jul 2013 14:26:53 +0900 From: Francois Berenger User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7 MIME-Version: 1.0 To: caml-list@inria.fr References: <1374669368.25411.5@samsung> <1B6BB035-9909-4F0C-9DEA-F713B977A467@ocamlpro.com> <7F8931D5-E65D-49EB-B54D-A50716F3EFDD@recoil.org> <51F0801A.5080603@riken.jp> <20130725172359.a40fdfb172b120cadab5544a@gmerlin.de> <20130725200356.GA15673@notk.org> <51F1CD6C.3050305@riken.jp> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.7.26.51822 Subject: [Caml-list] Re: ocamlbuild On 07/26/2013 02:02 PM, Gabriel Scherer wrote: > I am not very interested in build systems. Me neither. And, I'm not even competent enough to write one, unlike the many others who felt they have to do so. However, I do think (as a programmer) that the build system must _NEVER_ get in front of my way. It must be simple and observable (so that any problem with the build configuration is easily fixed by anyone) and parallelize the build to the maximum (this one should be a requirement from day 0 of the project). > I use one (ocamlbuild) that > I find decent (has several known areas of improvement, but bear with > me), and instead of rewriting a new one from scratch¹ I decided that > maybe the existing one I could be improved to fix its shortcomings. At some point, I feel that some things have to be redesigned from scratch rather than being patched endlessly. Or, just switch to a better tool if it already exists. > You know, by writing bug reports, and more importantly proposing > patches (to the code or the documentation), instead of just > complaining on the mailing-list. You know, especially you Gabriel, that I can do that (send patches with code, bug reports, etc.). However, I do this only for projects that I admire. Projects with a simple, crystal clear and sound design and a plain UNIX taste. > I'm not aware, so far, of a major > design problem that can't be incrementally fixed, and whose resolution > is worth the pain of switching to a completely new system. I'm not sure there will be any pain for me to switch to another build system (I think I will go for obuild). I've stayed too long with ocamlbuild obviously. Regards, Francois.