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=2.0 required=5.0 tests=AWL,DNS_FROM_RFC_POST, MISSING_HEADERS,SPF_NEUTRAL autolearn=disabled version=3.1.3 X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by yquem.inria.fr (Postfix) with ESMTP id F2310BBAF for ; Sat, 7 Feb 2009 22:13:40 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AmMDACuIjUnRVdwLkGdsb2JhbACNC4YPXz8BAQEBCQkMBxEDqUEIfo1AAQMBA4QXBoIxgSU X-IronPort-AV: E=Sophos;i="4.37,397,1231110000"; d="scan'208";a="20788441" Received: from mail-fx0-f11.google.com ([209.85.220.11]) by mail2-smtp-roc.national.inria.fr with ESMTP; 07 Feb 2009 22:13:40 +0100 Received: by fxm4 with SMTP id 4so4658688fxm.9 for ; Sat, 07 Feb 2009 13:13:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :user-agent:mime-version:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=lrilF8hXSu1d5vjxGn+LoG6z0WneaQt10Zv+Da2X4Mw=; b=a6QsmseiRMg/5dQcw6p7EuRKnd0nNF6/C3k6F7c/8nm9awM+8RApLnKypNAqSL+atL 6Hk/lEEKdsaQIdx1cFPZeMHpGIdPcAbUnnpAW0sikvD2IQXZU/oaV7qTTbumqkUP6eD3 gCo4nju1z/KiCSfvLJWJpMnqe+QJ2u8Uy6haw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:user-agent:mime-version:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=gD3UkMlWEaT38Vb6rSDr+7efOJ6RbspqRT2qgZK9NfBeQrowf/QKOVzr2MIjQHP4Gl gL8r9Y2aTJNYqH0LSLYb7yAZA2u1mAYfalVXgbxJgc4bjvS4EVN9/SNHz44cOITh3v0A oYFocq3900NsjtehoUhyUiDLIqzE9rViVyaxY= Received: by 10.103.160.3 with SMTP id m3mr1392199muo.25.1234041219959; Sat, 07 Feb 2009 13:13:39 -0800 (PST) Received: from ?192.168.1.10? (8.75.197-77.rev.gaoland.net [77.197.75.8]) by mx.google.com with ESMTPS id 7sm1429178mup.19.2009.02.07.13.13.39 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 07 Feb 2009 13:13:39 -0800 (PST) Message-ID: <498DF981.5000609@gmail.com> Date: Sat, 07 Feb 2009 22:13:37 +0100 From: Matthieu Dubuget Reply-To: matthieu.dubuget@gmail.com User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 Cc: caml-list@inria.fr Subject: Re: [Caml-list] Re: [ANN] OCaml Batteries Included, alpha 3 References: <1233936696.6216.65.camel@Blefuscu> <200902071458.45000.jon@ffconsultancy.com> <498DB32B.8090005@gmail.com> <1234035013.6797.3.camel@Blefuscu> In-Reply-To: <1234035013.6797.3.camel@Blefuscu> X-Enigmail-Version: 0.95.0 OpenPGP: id=F60AB8F5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam: no; 0.00; matthieu:01 dubuget:01 matthieu:01 dubuget:01 ocaml:01 0100,:01 modular:01 copy-paste:01 findlib:01 findlib:01 ocamlfind:01 ocamlfind:01 dependencies:01 2009:98 wrote:01 David Rajchenbach-Teller a écrit : > On Sat, 2009-02-07 at 17:13 +0100, Matthieu Dubuget wrote: >> An other points that could be improved, concerning ocamlbuild are: >> - modules (planned, but I don't know how many time the owners of >> ocamlbuild have?) > > I don't quite understand this. >>From the very beginning, I had the feeling that ocamlbuild's author had planned to make the monolithic myocamlbuild system more modular. I may be wrong. My idea is that it would be very useful if one could specify other modules to compile and use (and the associated command line if necessary) instead of copy-paste everything needed into myocamlbuild. > >> - better integration with findlib (modules would help, and also the >> possibility to use directly findlib modules from ocamlbuild modules) > > The myocamlbuild.ml provided with Batteries Included manages findlib > (that's actually based on an extract provided in the documentation of > OCamlBuild). Yes. I'm aware of that. But the tags associated to each package are constructed by calling ocamlfind as an external process, and parsing the output of ocamlfind. It would be cleaner and certainly more powerful if myocamlbuild module could use directly the findlib library provided with findlib? My development tree is composed of a lot of libraries. They have inter-dependencies. I would like to use ocamlfind more consistently, because this is very a nice tool. When properly configured, if I want to use Toto, i just have to add the toto package, and all dependencies and link options are sorted automatically. If I modify one library which is known by ocamlfind, I would like to be able to have all other packages that depends on it to be compiled again, and finally the target I'm working on. This not easy to achieve. And when I extract a fresh tree from my repository, I would like to have everything compiled and installed with an ocamlbuild all.otarget command. But I may be wrong by mixing the two levels: building with ocamlbuild and library use with ocamlfind. Sorry if all this is not clear, but it is not (yet) very clear for me… Salutations Matt P.S. When writing this post, I had a new idea that may simplify my problem: adding my development tree to findlib.conf path seems enough to let findlib find and use my own packages, without having to install them.