caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: "Jérémie Dimino" <jeremie@dimino.org>
Cc: "Daniel Bünzli" <daniel.buenzli@erratique.ch>,
	caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] oasis packaging questions
Date: Thu, 08 Mar 2012 17:19:35 +0100	[thread overview]
Message-ID: <1331223575.2826.288.camel@thinkpad> (raw)
In-Reply-To: <20120308170947.4847d3b3@caladan.esterel-technologies.com>

Am Donnerstag, den 08.03.2012, 17:09 +0100 schrieb Jérémie Dimino:
> Le Thu, 8 Mar 2012 01:26:38 +0100,
> Daniel Bünzli <daniel.buenzli@erratique.ch> a écrit :
> 
> > 1) All the packages I distribute are made of a single module. For now
> > these were just installed as .cmo .cmx .cmxs. Now it seems oasis
> > forces me to create a .mllib even if I have only one module. Is that
> > correct ? 
> 
> Note that in general it is better to install a cma/cmxa, even if your
> library has only one module. The reason is that when building an
> executable, cmo/cmx files passed on the command line are always linked,
> while unused units of cma/cmxa files are not (unless you specify
> -linkall).

Right. Just one refinement: if you also install the cmx _in addition to_
the cmxa, you enable cross-module inlining for this particular module.
This is completely optional. I usually do it only when I think it makes
sense. (Cannot comment on how this is handled in oasis.)

Gerd

> -- 
> Jérémie
> 
> 

-- 
------------------------------------------------------------
Gerd Stolpmann, Darmstadt, Germany    gerd@gerd-stolpmann.de
Creator of GODI and camlcity.org.
Contact details:        http://www.camlcity.org/contact.html
Company homepage:       http://www.gerd-stolpmann.de
*** Searching for new projects! Need consulting for system
*** programming in Ocaml? Gerd Stolpmann can help you.
------------------------------------------------------------



  reply	other threads:[~2012-03-08 16:19 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-08  0:26 Daniel Bünzli
2012-03-08  8:31 ` [Caml-list] " Sylvain Le Gall
2012-03-08 15:36   ` Daniel Bünzli
2012-03-08 20:13     ` Sylvain Le Gall
2012-03-08 20:59       ` Daniel Bünzli
2012-03-08 21:27         ` Sylvain Le Gall
2012-03-08 22:39           ` Daniel Bünzli
2012-03-09 11:56             ` Gerd Stolpmann
2012-03-09 13:53               ` Daniel Bünzli
2012-03-09 18:42           ` Daniel Bünzli
2012-03-09 19:11             ` Sylvain Le Gall
2012-03-09 19:49               ` Daniel Bünzli
2012-03-09 20:35               ` Daniel Bünzli
2012-03-09 21:06                 ` Sylvain Le Gall
2012-03-08 21:40       ` Adrien
2012-03-08 22:26         ` Sylvain Le Gall
2012-03-08 22:59           ` Daniel Bünzli
2012-03-09 12:22           ` Anil Madhavapeddy
2012-03-09 13:01             ` Wojciech Meyer
2012-03-12  0:38             ` Francois Berenger
2012-03-16 13:56     ` Damien Doligez
2012-03-08 16:09 ` [Caml-list] " Jérémie Dimino
2012-03-08 16:19   ` Gerd Stolpmann [this message]
2012-03-08 21:10     ` [Caml-list] " Sylvain Le Gall
2012-03-08 16:36   ` [Caml-list] " Daniel Bünzli
2012-03-08 16:58     ` Jérémie Dimino
2012-03-08 19:11       ` Daniel Bünzli
2012-03-09  6:40   ` Stéphane Glondu

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=1331223575.2826.288.camel@thinkpad \
    --to=info@gerd-stolpmann.de \
    --cc=caml-list@inria.fr \
    --cc=daniel.buenzli@erratique.ch \
    --cc=jeremie@dimino.org \
    /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).