caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: David Allsopp <dra-news@metastack.com>
To: Alexey Egorov <electreg@list.ru>, caml-list <caml-list@inria.fr>
Subject: RE: [Caml-list] OCaml for windows is abandoned?
Date: Sat, 21 Jan 2017 13:05:00 +0000	[thread overview]
Message-ID: <E51C5B015DBD1348A1D85763337FB6D901357F2E85@Remus.metastack.local> (raw)
In-Reply-To: <1485002648.357992658@f345.i.mail.ru>

Alexey Egorov wrote:
> Hello,
> 
> is there any plans for OCaml 4.04.0 for windows?

OCaml 4.04.0 has worked for Windows since its release (well, excepting an unfortunate regression on 64-bit Windows 10 - see GPR#912) but only built from sources.

> Official distribution is still at 4.02.3, and I'm unable to get any compiler from opam to work on windows.

Which OPAM have you been trying? This one should be working, thanks to the considerable efforts of @fdopen - https://fdopen.github.io/opam-repository-mingw/ and contains OCaml 4.03.0 and 4.04.0.

My fork of OPAM 2.0 (OPAM 2.0 itself is still in alpha development) at https://github.com/dra27/opam/tree/windows also builds OCaml (3.07-4.04), but you only get the compiler at the moment. There are corresponding repositories for it at https://github.com/dra27/opam-repository/tree/next-windows and https://github.com/dra27/windows-native (@fdopen's priority has been the package universe; mine is OS dependencies and compilers - the two will ultimately meet!)

I'm at present working on things towards OCaml 4.05 development, but I'm expecting to starting rebasing the Windows fork of OPAM 2.0 in the coming weeks.


David

  reply	other threads:[~2017-01-21 13:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-21 12:44 Alexey Egorov
2017-01-21 13:05 ` David Allsopp [this message]
2017-01-21 20:09   ` Alexey Egorov

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=E51C5B015DBD1348A1D85763337FB6D901357F2E85@Remus.metastack.local \
    --to=dra-news@metastack.com \
    --cc=caml-list@inria.fr \
    --cc=electreg@list.ru \
    /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).