Le Thu, 8 Mar 2012 01:26:38 +0100,
Daniel Bünzli daniel.buen...@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
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.buen...@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
Le jeudi, 8 mars 2012 à 17:09, Jérémie Dimino 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
Le jeudi, 8 mars 2012 à 17:58, Jérémie Dimino a écrit :
This may happen if you are using a subset of a multi-modules library
which use a single-module one.
Not completely unlikely I agree.
I'll go with the cma then.
Thanks,
Daniel
--
Caml-list mailing list. Subscription management
Le 08/03/2012 17:09, Jérémie Dimino 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
