From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: mikkelfj@gmail.com
Cc: caml-list@inria.fr
Subject: Re: Ocaml Win64 build?
Date: Thu, 22 Sep 2005 14:41:30 +0200 [thread overview]
Message-ID: <4332A67A.8010907@inria.fr> (raw)
In-Reply-To: <caee5ad80509180700433f1024@mail.gmail.com>
[ The question was asked on caml-list a while ago, and I forgot to
reply there, so this is Cc: to caml-list ]
> Do you have any plans to release Ocaml in an x86_64 bit version for Windows?
> Or a 32-bit version that can also generate 64-bit binaries? In fact,
> this would be preferable to having a 64-bit version that cannot
> generate 32-bit binaries.
This is on my "to do" list. This port will generate 64-bit binaries
only, but of course the 32-bit Windows port will still be there for
those who need to generate 32-bit binaries.
At this point, the main difficulty in this port is to set up a Win64
development machine. There are no Win64 machines in my vicinity, and
given the way purchase orders work at INRIA, it's unlikely there will
be one before March 2006.
Also, I could use recommendations and experience return about 64-bit
Windows development tools. What does Microsoft provides, preferably
for free? (What is needed: a C compiler, a linker, an assembler, and
import libraries for standard Windows DLLs.) Where is the reference
manual for the assembler syntax? (As usual, I couldn't find any
complete description in MSDN.) Any hints on when x86-64
versions of Mingw and Cygwin will be available?
Feel free to reply privately, as this isn't very topical for caml-list.
Regards,
- Xavier Leroy
next parent reply other threads:[~2005-09-22 12:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <caee5ad80509180700433f1024@mail.gmail.com>
2005-09-22 12:41 ` Xavier Leroy [this message]
2005-09-27 9:29 ` [Caml-list] " Dmitry Bely
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=4332A67A.8010907@inria.fr \
--to=xavier.leroy@inria.fr \
--cc=caml-list@inria.fr \
--cc=mikkelfj@gmail.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;
as well as URLs for NNTP newsgroup(s).