caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Török Edwin" <edwin+ml-ocaml@etorok.net>
To: caml-list@inria.fr
Subject: [Caml-list] Re: Library install standards
Date: Fri, 21 Dec 2012 22:59:59 +0200	[thread overview]
Message-ID: <50D4CDCF.9080507@etorok.net> (raw)
In-Reply-To: <50D4CB13.3020600@gmail.com>

On 12/21/2012 10:48 PM, Edgar Friendly wrote:
> On 12/21/2012 3:41 PM, Gerd Stolpmann wrote:
>> Am 21.12.2012 21:37:02 schrieb(en) Edgar Friendly:
>>> As a library author, should I install .cmt files for all my modules?  Should we make this the default in oasis?
>>
>> I guess wrappers for all the ocaml* commands would be enough. Or maybe a patch for ocaml. It would be painful if we had to change all the existing builds.
> Wrapping the ocaml* commands seems reasonable, but I was asking a more general question about what files should be installed for libraries.
> 
> 1) .cma and .cmxa files clearly need to be installed for linking

.a and .so too.

> 2) .cmi files need to be installed for compiling (?)
> 3) .cmx files should be installed for cross-module inlining / optimization

are .cmx files needed when .cmxa is available?

> 4) .cmt files for compiler tools
> 5) .mli files for users to read directly (optional)
> 6) Any .cmo files not put into .cma libraries
> What am I forgetting?

.cmxs, but oasis handles that already.
And of course a META file, but thats implied.

Best regards,
--Edwin

  reply	other threads:[~2012-12-21 21:00 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-20 23:15 [Caml-list] OCaml wiki Wojciech Meyer
2012-12-20 23:19 ` Malcolm Matalka
2012-12-20 23:22 ` Anil Madhavapeddy
2012-12-20 23:31   ` Benedikt Meurer
2012-12-20 23:34     ` Anil Madhavapeddy
2012-12-20 23:38       ` Malcolm Matalka
2012-12-20 23:50       ` Wojciech Meyer
2012-12-21  2:49         ` Ashish Agarwal
2012-12-21  8:37           ` Philippe Veber
2012-12-21  9:13             ` Fermin Reig
2012-12-21  9:39               ` Philippe Veber
2012-12-21 13:05           ` Wojciech Meyer
2012-12-21 13:31             ` Adrien
2012-12-21 16:39             ` Ashish Agarwal
2012-12-21 15:33           ` Siraaj Khandkar
2012-12-21 17:52             ` Siraaj Khandkar
2012-12-21 13:00     ` Hezekiah M. Carty
2012-12-21  1:31 ` [Caml-list] OCaml search into libraries for ocaml.org Francois Berenger
2012-12-21  2:57   ` Ashish Agarwal
2012-12-21  7:34     ` forum
2012-12-21 15:31       ` Leo White
2012-12-21 19:57   ` AW: " Gerd Stolpmann
2012-12-21 20:22     ` Török Edwin
2012-12-21 20:34       ` AW: " Gerd Stolpmann
2012-12-21 20:37         ` Edgar Friendly
2012-12-21 20:41           ` AW: " Gerd Stolpmann
2012-12-21 20:48             ` Library install standards (was: Re: AW: AW: AW: [Caml-list] OCaml search into libraries for ocaml.org) Edgar Friendly
2012-12-21 20:59               ` Török Edwin [this message]
2012-12-21 23:47                 ` AW: [Caml-list] Re: Library install standards Gerd Stolpmann
2012-12-21 16:20 ` [Caml-list] OCaml wiki Vincent Balat
2012-12-21 16:45   ` Ashish Agarwal
2012-12-23 14:53     ` Vincent Balat
2012-12-25  1:14       ` Ashish Agarwal

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=50D4CDCF.9080507@etorok.net \
    --to=edwin+ml-ocaml@etorok.net \
    --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).