From: William Smith <bills@emu-bark.com>
To: OCAML <caml-list@inria.fr>
Subject: [Caml-list] MSVC port of ocaml-4.00.1
Date: Fri, 16 Nov 2012 13:58:52 -0500 [thread overview]
Message-ID: <50A68CEC.5030204@emu-bark.com> (raw)
Hi,
I am building a microsoft visual C 32 bit version of ocaml-4.00.1 from
the distribution sources. It's been very difficult.
I have been forced to make substantial changes to flexdll 0.30 to make
it work. I'm still trying to find a minimal patch to flexdll that
works. The flexdll changes are restricted to the MSVC compile chain, so
that when I get a patch put together it won't break the other tools.
There are also a number of changes I will make to README.win32 to
explain about more of the environment variables that are required. I've
found some additional environment variables. Also, some have specific
restrictions on their content.
Has anyone else put together an MSVC OCaml 4?
Bill Smith
next reply other threads:[~2012-11-16 18:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 18:58 William Smith [this message]
2012-11-16 23:33 ` Alain Frisch
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=50A68CEC.5030204@emu-bark.com \
--to=bills@emu-bark.com \
--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).