From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: jeanmarc.eber@lexifi.com
Cc: caml-list@inria.fr, david.vincent@lexifi.com
Subject: Re: -custom under win32
Date: Tue, 23 Jan 2001 10:45:06 +0100 [thread overview]
Message-ID: <20010123104506.B5637@pauillac.inria.fr> (raw)
In-Reply-To: <980184766.3a6c6ebe3620e@imp.pro.proxad.net>; from jeanmarc.eber@lexifi.com on Mon, Jan 22, 2001 at 06:32:46PM +0100
> Hi OCamler!
>
> I want to generate a "closed bytecode" executable under win32 (that
> contains the bytecode interpreter so that it can be used on a
> machine without OCaml installed). I'm just using the "standard"
> Ocaml run-time (I haven't written any C-code to incorporate in the
> run-time).
>
> 1. Do I understand well that I need the Microsoft Linker (cl.exe),
> but ONLY the linker, not the C compiler or assembler ?
You don't need the assembler, however you need the C libraries in
addition to the linker, so it looks like the full VC++ is needed to
get "ocamlc -custom" to work.
BUT: if there is no C code in your program, you can build a closed
bytecode executable just by concatenating the standard bytecode
interpreter with your bytecode executable:
copy /b \ocaml\bin\ocamlrun.exe+mybytecode.exe standalone.exe
or if you prefer the Unix-like way:
cat /ocaml/bin/ocamlrun.exe mybytecode.exe > standalone.exe
Easy, wasn't it.
> 2. If yes, does anybody know if this linker can be obtained/purchased/...
> without buying VC++ ?
No idea.
> 3. Can my problem be solved with Cygwin now, in a future version ?
The next release of OCaml will contain a Cygwin port, so you'll be
able to do "ocamlc -custom" without buying VC++. I think you'll need
to distribute the Cygwin DLL along with the generated executable,
though.
- Xavier Leroy
next prev parent reply other threads:[~2001-01-23 21:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-22 17:32 jeanmarc.eber
2001-01-23 9:45 ` Xavier Leroy [this message]
2001-01-24 18:36 ` Lionel Fourquaux
2001-01-23 10:49 ` Lionel Fourquaux
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=20010123104506.B5637@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=caml-list@inria.fr \
--cc=david.vincent@lexifi.com \
--cc=jeanmarc.eber@lexifi.com \
/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