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.2 required=5.0 tests=AWL autolearn=disabled version=3.1.3 X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by yquem.inria.fr (Postfix) with ESMTP id 6141CBB84 for ; Wed, 24 Sep 2008 22:09:59 +0200 (CEST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvICAHY72kjAXQIniGdsb2JhbACTKAEBARUiqj2BZQ X-IronPort-AV: E=Sophos;i="4.33,303,1220220000"; d="scan'208";a="29550589" Received: from concorde.inria.fr ([192.93.2.39]) by mail4-smtp-sop.national.inria.fr with ESMTP; 24 Sep 2008 22:09:58 +0200 Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by concorde.inria.fr (8.13.6/8.13.6) with ESMTP id m8OK9wo0024556 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=OK) for ; Wed, 24 Sep 2008 22:09:58 +0200 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqwBAAM72khQW+UCgWdsb2JhbACTKAEBFiIEqjiBZQ X-IronPort-AV: E=Sophos;i="4.33,303,1220220000"; d="scan'208";a="17708448" Received: from main.gmane.org (HELO ciao.gmane.org) ([80.91.229.2]) by mail1-smtp-roc.national.inria.fr with ESMTP/TLS/AES256-SHA; 24 Sep 2008 22:09:57 +0200 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1KiagM-0007O9-V5 for caml-list@inria.fr; Wed, 24 Sep 2008 20:09:54 +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, 24 Sep 2008 20:09:54 +0000 Received: from sylvain by ks300734.kimsufi.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 24 Sep 2008 20:09:54 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: caml-list@inria.fr From: Sylvain Le Gall Subject: Re: What's the purpose of the static library? Date: Wed, 24 Sep 2008 20:09:46 +0000 (UTC) Message-ID: References: <48D712A8.6090506@sun.com> <48D766CC.5020401@glondu.net> <48D8B266.4000906@sun.com> <20080923101710.GA29133@annexia.org> 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/pre0.9.9-102 (Linux) Sender: news X-Miltered: at concorde with ID 48DA9E96.000 by Joe's j-chkmail (http://j-chkmail . ensmp . fr)! X-Spam: no; 0.00; le-gall:01 cmx:01 cmx:01 ml':01 compiler:01 cmxa:01 inlining:01 23,:98 wrote:01 wrote:01 linking:02 linking:02 native:03 native:03 module:03 On 23-09-2008, Richard Jones wrote: > On Tue, Sep 23, 2008 at 05:09:58PM +0800, bill yan wrote: > > Files: module.o and module.cmx -------------------- > > These two files go together. The *.o file contains compiled native > code in the normal system object file format. The *.cmx file contains > metainformation about the machine code in the *.o file. > > Created by: 'ocamlopt -c module.ml' > > Used: When linking native code programs, or creating native code > libraries. > > Note(1): You normally never need to specify the *.o files by hand. On > the command line when the compiler sees a *.cmx file, it looks for the > corresponding *.o file if it needs it. > > Note(2): It is thought that the *.cmx file needs to be around even > when linking a library (*.cmxa) file in order to do cross-module > function inlining. Both the Debian & Fedora packaging rules specify > that *.cmx files be kept around for this reason. Whether this is > really true or not is not certain. > Do you think *.cmx and *.o should be shipped? Is *.cmx enough? Regards Sylvain Le Gall