From: Xavier Leroy <xavier.leroy@inria.fr>
To: Dimitri Timofeev <dt@dt7463.spb.edu>
Cc: OCaml mailing list <caml-list@inria.fr>
Subject: Re: [Caml-list] Dynamic module loading
Date: Sun, 11 Nov 2001 17:45:54 +0100 [thread overview]
Message-ID: <20011111174554.A16307@pauillac.inria.fr> (raw)
In-Reply-To: <Pine.LNX.4.30.0111101813540.1450-100000@localhost.localdomain>; from dt@dt7463.spb.edu on Sat, Nov 10, 2001 at 06:27:12PM -0500
Your first question was answered, so let me address the second one:
> If i can't use native-compiled modules only, there is another question.
> That is the minimal set of OCaml files i need to distribute with a
> program if i want users to be able to run program compiled to bytecode
> without installing OCaml itself?
No additional files are needed if you perform the final link with
"ocamlc -custom". This will create a stand-alone executable
incorporating the OCaml bytecode interpreter, runtime system, and the
bytecode for your program.
Correction: the OCaml runtime system is a C program, and as such can
require certain DLLs containing the C runtime. Under Unix, you can
even force static linking of these C runtime libs using
ocamlc -ccopt -static -custom
Under Windows, no such -static option exists, and you'll have to
ensure the users have the required DLLS (winsock.dll for the pure
Win32 port of OCaml, cygwin1.dll for the Cygwin port).
- Xavier Leroy
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-11-11 16:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-10 23:27 Dimitri Timofeev
2001-11-11 0:15 ` Michael Hicks
2001-11-11 22:09 ` Vitaly Lugovsky
2001-11-12 11:22 ` Fabrice Le Fessant
2001-11-11 1:00 ` malc
2001-11-11 16:45 ` Xavier Leroy [this message]
2001-11-12 5:21 Dimitri Timofeev
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=20011111174554.A16307@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=caml-list@inria.fr \
--cc=dt@dt7463.spb.edu \
/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).