caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Yotam Barnoy <yotambarnoy@gmail.com>
Cc: Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Thoughts on targeting windows
Date: Mon, 9 Jun 2014 08:06:46 -0400	[thread overview]
Message-ID: <CAN6ygOmWhXYHAbwfJFEzOUwkMOF5_OnzdTC7JkYmUorg=Y9uNA@mail.gmail.com> (raw)
In-Reply-To: <53957B83.2000003@coherentgraphics.co.uk>

[-- Attachment #1: Type: text/plain, Size: 2066 bytes --]

Speaking of which, are there any updates on the Windows situation with
regard to opam and Core? Specifically with regard to Core, I find it odd
that Ocaml's most popular (and well-written) book doesn't support the most
popular OS in the world.

-Yotam


On Mon, Jun 9, 2014 at 5:16 AM, John Whitington <john@coherentgraphics.co.uk
> wrote:

> Hi,
>
>
> William wrote:
>
>> Hi all,
>>
>> we are considering using OCaml for a rather large project, the bulk of
>> which will be networking and encryption. OCaml seems to meet our needs
>> with one exception:
>> we'd like to target windows (as well as linux & mac) and we got the
>> impression that this would be complicated -- we gathered that neither
>> jane street's Core nor OPAM are windows compatible.
>>
>> Would still recommend using OCaml? Are there workarounds, or other
>> libraries that would replace Core?
>>
>
> Here is the Windows installer:
>
> http://protz.github.io/ocaml-installer/
>
> This also installs 'ocamlfind', which means that you can download source
> packages for libraries you're interested in, compile them, install them and
> use them relatively easily. Not as convenient as OPAM, of course.
>
> Here is a library for cryptography:
>
> https://forge.ocamlcore.org/projects/cryptokit/
>
> Here is a library for concurrency which runs on Windows:
>
> http://ocsigen.org/lwt/
>
> Here is a different Standard Library replacement/augmentation:
>
> https://github.com/ocaml-batteries-team/batteries-included
>
> (The software I build for Windows, whilst complex in terms of what it
> does, is just a single statically linked executable which reads a file,
> processes it and writes a file, so I can't tell you anything about
> networking under Windows.)
>
> Thanks,
>
> --
> John Whitington
> Director, Coherent Graphics Ltd
> http://www.coherentpdf.com/
>
>
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>

[-- Attachment #2: Type: text/html, Size: 3451 bytes --]

  reply	other threads:[~2014-06-09 12:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-09  8:56 William
2014-06-09  9:13 ` Virgile Prevosto
2014-06-09  9:16 ` John Whitington
2014-06-09 12:06   ` Yotam Barnoy [this message]
2014-06-09 12:26     ` Matthieu Dubuget
2014-06-09 15:23 ` David Allsopp
2014-06-09 18:59   ` Yaron Minsky
2014-06-09 19:34     ` Sebastien Mondet
2014-06-09 20:06       ` Yaron Minsky
2014-06-10  9:53         ` Thomas Gazagnaire
2014-10-05 22:14   ` Anil Madhavapeddy
2014-10-09  9:33     ` Jeremy Yallop
2014-12-10  9:57       ` Anil Madhavapeddy

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='CAN6ygOmWhXYHAbwfJFEzOUwkMOF5_OnzdTC7JkYmUorg=Y9uNA@mail.gmail.com' \
    --to=yotambarnoy@gmail.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).