From: ls-ocaml-developer-2006@m-e-leypold.de
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Re: stand-alone top-level
Date: Tue, 17 Apr 2007 18:11:35 +0200 [thread overview]
Message-ID: <qlkgrf0aw.fsf@hod.lan.m-e-leypold.de> (raw)
In-Reply-To: <4624D87D.9020906@podval.org> (Sam Steingold's message of "Tue, 17 Apr 2007 10:23:57 -0400")
Sam Steingold <sds@podval.org> writes:
> EL CHAAR Rabih SGAM/AI/SAM wrote:
>> If you speak about the toplevel as interactive, it needs to see the
>> modules interfaces in order to do the type checking, compilation,
>> ... These were always in cmi files, which are not embedded in
>> libraries (cma or cmxa).
>
> it would be nice if they were optionally embeddable in the interactive
> top-level.
I suggest tar-ing the *.cmi and the toplevel together, copying them to
the target machine and un-tar-ing? Or rsyncing a complete directory?
You could automate all this with a script.
Regards -- Markus
prev parent reply other threads:[~2007-04-17 16:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-17 14:14 EL CHAAR Rabih SGAM/AI/SAM
2007-04-17 14:23 ` Sam Steingold
2007-04-17 16:11 ` ls-ocaml-developer-2006 [this message]
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=qlkgrf0aw.fsf@hod.lan.m-e-leypold.de \
--to=ls-ocaml-developer-2006@m-e-leypold.de \
--cc=caml-list@yquem.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).