From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 97C167EE4B for ; Mon, 30 Sep 2013 10:07:19 +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: AnoBAAgwSVKGoCGinGdsb2JhbABagz/BTIE8DgEBAQEBCAsJCRQogiUBAQU4QBEjCRYPCQMCAQIBRRMIAQGIArw4jgKBVhaEDAOJN45IgS+FBI0sgU0 X-IPAS-Result: AnoBAAgwSVKGoCGinGdsb2JhbABagz/BTIE8DgEBAQEBCAsJCRQogiUBAQU4QBEjCRYPCQMCAQIBRRMIAQGIArw4jgKBVhaEDAOJN45IgS+FBI0sgU0 X-IronPort-AV: E=Sophos;i="4.90,1006,1371074400"; d="scan'208";a="28514375" Received: from postman2.riken.jp (HELO postman.riken.jp) ([134.160.33.162]) by mail3-smtp-sop.national.inria.fr with ESMTP; 30 Sep 2013 10:07:17 +0200 Received: from postman.riken.jp (postman2.riken.jp [127.0.0.1]) by postman.riken.jp (Postfix) with SMTP id 54FDF126066B for ; Mon, 30 Sep 2013 17:07:16 +0900 (JST) Received: from [172.27.98.103] (rikad98.riken.jp [134.160.214.98]) by postman.riken.jp (Postfix) with ESMTPA id 12EBE1270051 for ; Mon, 30 Sep 2013 17:07:16 +0900 (JST) Message-ID: <5249310F.7090108@riken.jp> Date: Mon, 30 Sep 2013 17:06:39 +0900 From: Francois Berenger User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: caml-list@inria.fr References: <5229DEF9.7040706@inria.fr> <5229F284.5050806@inria.fr> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.9.30.75714 Subject: [Caml-list] from oasis to obuild (original subject was Re: Accelerating compilation) On 09/07/2013 05:51 AM, Fabrice Le Fessant wrote: > [...] > FWIW, I recently compiled Merlin with both ocamlbuild and ocp-build, > on a quad-core with "-j 10" for both (the link to the ocp-build > description file is in the latest OCamlPro's report), ocamlbuild needs > 13s where ocp-build only needs 4s to compile everything. I recently switched from oasis to obuild. The main reason I adopted oasis in the past is because the project description file (_oasis) is very short. With ocp-build, (as far as I know) I would have to list all the files my program/libraries need to be built, and I am too lazy for that. But now, I have a project.obuild file instead, which is as terse as an _oasis file. Here is my project.obuild file: --- Name: something Version: 0.1 Authors: me License: GPL Synopsis: some_more_things obuild-ver: 1 Executable ac Path: . BuildDepends: batteries, dolog, parmap, vector3, biniou, atd, atdgen MainIs: ac.ml [...] some other executables follow --- Compile time before, with oasis: # cat build.sh #!/bin/bash #set -x oasis setup ocaml setup.ml -configure ocaml setup.ml -build # time ./build.sh real 0m9.397s Compile time after, with obuild: # obuild clean && time (obuild configure && obuild build -j 1) real 0m3.624s -- Best regards, Francois Berenger.