From: skaller <skaller@users.sourceforge.net>
To: caml-list <caml-list@inria.fr>
Subject: windows ocaml
Date: Tue, 19 Jun 2007 15:50:42 +1000 [thread overview]
Message-ID: <1182232242.29571.157.camel@rosella.wigram> (raw)
Hi, we're having a terrible time getting ocaml to work properly
on Windows. This is with 3.09 native build.
1. ocamlc makes a bytecode file without an extension, which
cannot be executed. Ocamlopt adds '.exe'. This is inconsistent.
2. ocamlc makes a bytecode file which, when you add .exe
to the end can't exec ocamlrun .. even though it is in the PATH.
ocamlrun filename works fine.
The way our build scripts are set up, we assume the generated
file from a link step is executable (as for native code compiler).
For transparency, the generated bytecode must use the same filename
(.exe must be added) and the bytecode must actually run.
It looks like the bytecode is binding the wrong ocamlrun location,
if the bytecode file is copied to the same directory as contains
ocamlrun, it runs .. otherwise it fails.
--
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net
next reply other threads:[~2007-06-19 5:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 5:50 skaller [this message]
2007-06-19 7:28 ` [Caml-list] " Christophe TROESTLER
2007-06-19 9:25 ` skaller
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=1182232242.29571.157.camel@rosella.wigram \
--to=skaller@users.sourceforge.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).