From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by walapai.inria.fr (8.13.6/8.13.6) with ESMTP id q28GwOJ7030292 for ; Thu, 8 Mar 2012 17:58:24 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AiEFAOzkWE/VuiYS/2dsb2JhbABChGxWr2iBB4IKAQEEAQwXVhAJAhoCJgICVwYTiAUJrHyKTIEvjimBFgSVRJAZgmQ X-IronPort-AV: E=Sophos;i="4.73,552,1325458800"; d="scan'208";a="148291118" Received: from solaria.dimino.org ([213.186.38.18]) by mail1-smtp-roc.national.inria.fr with ESMTP/TLS/ADH-AES256-SHA; 08 Mar 2012 17:58:18 +0100 Received: from caladan (caladan.dim [10.200.42.14]) by solaria.dimino.org (Postfix) with ESMTP id 3C8B980053; Thu, 8 Mar 2012 17:58:18 +0100 (CET) Received: from caladan.esterel-technologies.com (localhost [127.0.0.1]) by caladan (Postfix) with ESMTP id AAEE3FF834; Thu, 8 Mar 2012 17:58:02 +0100 (CET) Date: Thu, 8 Mar 2012 17:58:01 +0100 From: =?UTF-8?B?SsOpcsOpbWll?= Dimino To: Daniel =?UTF-8?B?QsO8bnpsaQ==?= Cc: caml-list Message-ID: <20120308175801.54ca2421@caladan.esterel-technologies.com> In-Reply-To: <2BC2638DE3FA453FA8895253AAD1F32C@erratique.ch> References: <1991A512A37E49ACA5AAD30A38D628BF@erratique.ch> <20120308170947.4847d3b3@caladan.esterel-technologies.com> <2BC2638DE3FA453FA8895253AAD1F32C@erratique.ch> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.9; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by walapai.inria.fr id q28GwOJ7030292 Subject: Re: [Caml-list] oasis packaging questions Le Thu, 8 Mar 2012 17:36:46 +0100, Daniel Bünzli a écrit : > > 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). > > Okay, but is there a reasonable case (beyond sloppy dependency > tracking) where you'd like to link against a *single module* library > while not wanting to use it ? This may happen if you are using a subset of a multi-modules library which use a single-module one. -- Jérémie