caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Chris Conway <cconway@cs.nyu.edu>
To: caml-list@inria.fr
Subject: Re: What's the purpose of the static library?
Date: Tue, 23 Sep 2008 12:49:38 +0000 (UTC)	[thread overview]
Message-ID: <loom.20080923T124233-7@post.gmane.org> (raw)
In-Reply-To: <20080923101710.GA29133@annexia.org>


Richard Jones <rich <at> annexia.org> writes:
> <...>
> File: module.cmo ------------------------------
> 
> Contains the bytecode of the implementation of Module.
> 
> Created by: 'ocamlc -c module.ml'
> 
> Used: When linking bytecode programs, or creating bytecode libraries
> (*.cma), or by the toplevel when you use #load, or by Dynlink.
> 
> File: library.cma ------------------------------
> 
> This is just a set of *.cmo files combined together.
> 
> Created by: 'ocamlc -a'
> 
> Used: Same as for module.cmo

Richard,

This is a wonderful answer! It should go onto the wiki or in the FAQ. 
One nitpick...

.cma (and .cmxa) files should not be used for creating libraries 
(as .cmo and .cmx files can (and should) be). I.e., don't like a 
library into a library. Doing so will give a compiler error: 
    X.cma is not a compilation unit description.

Regards,
Chris



  parent reply	other threads:[~2008-09-23 12:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-22  3:36 bill yan
2008-09-22  9:35 ` [Caml-list] " Stéphane Glondu
2008-09-23  9:09   ` bill yan
2008-09-23 10:17     ` Richard Jones
2008-09-23 11:42       ` Alain Frisch
2008-09-23 12:49       ` Chris Conway [this message]
2008-09-24 11:24       ` Stefano Zacchiroli
2008-09-24 17:28         ` Richard Jones
2008-09-24 20:09       ` Sylvain Le Gall
2008-09-25 10:58       ` [Caml-list] " bill yan
2008-09-25 11:11         ` Alain Frisch
2008-10-08  3:20           ` bill yan
2008-10-08  3:29             ` bill yan
2008-09-23 10:24     ` Daniel Bünzli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=loom.20080923T124233-7@post.gmane.org \
    --to=cconway@cs.nyu.edu \
    --cc=caml-list@inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).