Sorry, I just noticed Richard already answered my question in previous
email. So Please ignore my previous email. Thanks.
bill yan 已写入:
Thanks for the help. Another question, It seems *.cma *.cmxa *.a are
all native code libraries, why are there so many suffix? Is there any
difference between
Thanks for the help. Another question, It seems *.cma *.cmxa *.a are all
native code libraries, why are there so many suffix? Is there any
difference between cma, cmxa and a?
Alain Frisch 已写入:
bill yan wrote:
By my understanding, unlike dlllibrary.so and liblibrary.a give user
an option to
bill yan wrote:
By my understanding, unlike dlllibrary.so and liblibrary.a give user an
option to choose compile dynamically or staticly, it seems for
library.a, user can only choose static method. Does that mean "compiled
native code" can only be staticly linked to user's application?
In
Hi Richard,
Thanks a lot for your help on this topic. Now I have a quesiton for the
following part:
File: library.a and library.cmxa
These files go together. The *.a file contains compiled native code
in the normal system archive format. The *.cmxa file contains
metain
On Wed, Sep 24, 2008 at 01:24:54PM +0200, Stefano Zacchiroli wrote:
> On Tue, Sep 23, 2008 at 11:17:11AM +0100, Richard Jones wrote:
> > It's not particularly well-documented, and it changes a little in
> > 3.11, but below is my understanding. There are probably errors in
> > what follows. If som
On Tue, Sep 23, 2008 at 11:17:11AM +0100, Richard Jones wrote:
> It's not particularly well-documented, and it changes a little in
> 3.11, but below is my understanding. There are probably errors in
> what follows. If someone can correct the errors then I'll publish a
> corrected document.
Hi Ri
Richard Jones wrote:
File: library.cma --
This is just a set of *.cmo files combined together.
Created by: 'ocamlc -a'
Used: Same as for module.cmo
.cma files also contain extra linking directives like references to C
libraries.
Files: module.o and module.cmx
Le 23 sept. 08 à 11:09, bill yan a écrit :
And we'd like to know more about the OCaml library architectures,
like on what situation dynamic libraries are used, and when static
libraries are used, and so on..
This depends on what _you_ want. The tradeoffs of dynamic vs static
linking are
On Tue, Sep 23, 2008 at 05:09:58PM +0800, bill yan wrote:
> Thanks a lot for your information. And we'd like to know more about the
> OCaml library architectures, like on what situation dynamic libraries
> are used, and when static libraries are used, and so on.. Really
> appreciate if you could
Hi Stéphane,
Thanks a lot for your information. And we'd like to know more about the
OCaml library architectures, like on what situation dynamic libraries
are used, and when static libraries are used, and so on.. Really
appreciate if you could point me to a document that can help on this topic
bill yan a écrit :
I noticed there are some static libraries(.a) installed with ocaml, for
example, /usr/lib/ocaml/bigarray.a. What's the purpose of those static
libraries? Thanks a lot.
They contain (natively) compiled OCaml code. An OCaml library compiled
in native mode (usually) consists of
Hi,
I noticed there are some static libraries(.a) installed with ocaml, for
example, /usr/lib/ocaml/bigarray.a. What's the purpose of those static
libraries? Thanks a lot.
Regards,
Bill
___
Caml-list mailing list. Subscription management:
http://yquem.
12 matches
Mail list logo