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.0 required=5.0 tests=none autolearn=disabled version=3.1.3 X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from discorde.inria.fr (discorde.inria.fr [192.93.2.38]) by yquem.inria.fr (Postfix) with ESMTP id B97AABC0A for ; Sat, 24 Mar 2007 16:26:37 +0100 (CET) Received: from smtp3-g19.free.fr (smtp3-g19.free.fr [212.27.42.29]) by discorde.inria.fr (8.13.6/8.13.6) with ESMTP id l2OFQbrO008610 for ; Sat, 24 Mar 2007 16:26:37 +0100 Received: from [192.168.0.1] (rke75-3-82-229-183-156.fbx.proxad.net [82.229.183.156]) by smtp3-g19.free.fr (Postfix) with ESMTP id 2FAE55B34B; Sat, 24 Mar 2007 16:26:37 +0100 (CET) Message-ID: <4605432C.4030105@inria.fr> Date: Sat, 24 Mar 2007 16:26:36 +0100 From: Alain Frisch User-Agent: Icedove 1.5.0.8 (X11/20061116) MIME-Version: 1.0 To: Christian Sternagel Cc: caml-list@inria.fr Subject: Re: [Caml-list] generating .cma-files with ocamlbuild References: <1174749088.46053fa061126@web-mail1.uibk.ac.at> In-Reply-To: <1174749088.46053fa061126@web-mail1.uibk.ac.at> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Miltered: at discorde with ID 4605432D.000 by Joe's j-chkmail (http://j-chkmail . ensmp . fr)! X-Spam: no; 0.00; frisch:01 frisch:01 mli:01 util:01 cmo:01 wrote:01 caml-list:01 incompatible:01 interfaces:01 cma:01 cma:01 alain:01 alain:01 modules:02 module:03 Christian Sternagel wrote: > Is there an easy way to tell ocamlbuild that it should > take some *.ml and *.mli files and build an archive > .cma out of them? Yes, just create a .mllib file that lists all the modules you want to include in the .cma. > 1) Is my understandung correct? Yes, it is. > 2) Can there be a problem if somebody using util.cma > (who does not know, that setInternal.cmo is part of > it) uses a self-made module by the name SetInternal > in his application? Indeed, the linker will complain about incompatible interfaces for the same module name. -- Alain