From: Christophe Raffalli <christophe.raffalli@univ-savoie.fr>
To: skaller <skaller@users.sourceforge.net>
Cc: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>,
daniel.buenzli@epfl.ch, caml-list@inria.fr
Subject: Re: [Caml-list] How to compile different implementations of the same lib
Date: Thu, 01 Dec 2005 22:33:02 +0100 [thread overview]
Message-ID: <438F6C0E.6080206@univ-savoie.fr> (raw)
In-Reply-To: <1133459647.9266.20.camel@rosella>
[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]
skaller a écrit :
> On Thu, 2005-12-01 at 18:03 +0100, Christophe Raffalli wrote:
>
>
>>May be I still do not get the problem
>
>
> Simple. Ocaml cheats. When you *compile* against a cmx
> or cmi/cmx pair, Ocaml 'cheats' and lifts non-interface
> information out of the cmx. This allows it to, for
> example, inline functions by cheating and grabbing their
> implementations from the cmx.
>
Yes, I knew that but ..
if I have
toto.cmi in /usr/lib/ocaml
toto.cmx and toto.o in /usr/lib/ocaml/totov1/ compiled from totov1.ml
toto.cmx and toto.o in /usr/lib/ocaml/totov2/ compiled from totov1.ml
tata.ml that does "open Toto"
then use either
ocamlopt -I +totov1 toto.cmx tata.ml
ocamlopt -I +totov2 toto.cmx tata.ml
shouldn't this work ?
Indeed, I tried using "the ln -s" trick for compilation as suggested ...
and it seems to work ?
It is a bit painfull both for compilation and usage ...
BTW: I can not miss inlinig for bindlib, since there will be many calls
to small functions (even 1 line ones) in code using bindlib (I guess,
but did not try).
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 894 bytes --]
next prev parent reply other threads:[~2005-12-01 21:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 9:05 Best way to choose an implementation of a lib ? Christophe Raffalli
2005-11-30 12:19 ` [Caml-list] " Jacques Garrigue
2005-11-30 14:38 ` How to compile different implementations of the same lib Daniel Bünzli
2005-11-30 16:09 ` [Caml-list] " Daniel Bünzli
2005-12-01 1:07 ` Jacques Garrigue
2005-12-01 1:53 ` malc
2005-12-01 17:03 ` Christophe Raffalli
2005-12-01 17:54 ` skaller
2005-12-01 20:09 ` Richard Jones
2005-12-01 23:47 ` skaller
2005-12-02 3:29 ` Jacques Garrigue
2005-12-01 21:33 ` Christophe Raffalli [this message]
2005-12-02 3:06 ` Jacques Garrigue
2005-11-30 16:24 ` how to detect .cmx incompatibility Stefano Zacchiroli
2005-11-30 19:48 ` [Caml-list] Best way to choose an implementation of a lib ? Eric Cooper
2005-12-01 17:05 ` Christophe Raffalli
2005-12-01 17:31 ` Eric Cooper
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=438F6C0E.6080206@univ-savoie.fr \
--to=christophe.raffalli@univ-savoie.fr \
--cc=caml-list@inria.fr \
--cc=daniel.buenzli@epfl.ch \
--cc=garrigue@math.nagoya-u.ac.jp \
--cc=skaller@users.sourceforge.net \
/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).