From: Bikal Gurung <bikal.gurung@lemaetech.co.uk>
To: David Allsopp <dra-news@metastack.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Ocaml on windows
Date: Mon, 24 Jun 2013 11:01:06 +0100 [thread overview]
Message-ID: <CAB-rfD0vdWWtvVaBsJoXJeU63EXhuyAK-j6mifW8h9E4spB-Uw@mail.gmail.com> (raw)
In-Reply-To: <E51C5B015DBD1348A1D85763337FB6D9CC8677FE@Remus.metastack.local>
[-- Attachment #1: Type: text/plain, Size: 1886 bytes --]
Hi David,
Thank you for your response. I have installed the official windows port of
ocaml at http://protz.github.io/ocaml-installer/ . However, it mentions
that MinGW/Msys is no longer supported. I rather use Mingw/Msys as well.
It seems ocamlbuild requires cygwin to work, has this been your experience
too? If I build the latest ocaml from trunk - 4.02dev+fp will ocaml and
other tools/utilities still work on pure MingWg/Msys environment?
With regards to ocaml libraries, have you tried the Jane Street packages?
Core, core_kernel ?
Bikal Gurung
On 24 June 2013 10:27, David Allsopp <dra-news@metastack.com> wrote:
> Bikal Gurung wrote:
> > I am looking to use ocaml to implement a project for my employer.
> However,
> > the environment is Windows OS. I am using cygwin and so far it seems to
> > work but curious on experiences others have on using ocaml on windows -
> > both as a development and deployment platform. Also has anyone tried
> using
> > opam on windows? Does it work?
>
> I've used the MinGW Windows port of OCaml for nearly a decade. Deployment
> of programs is the same as deploying anything else on Windows - deploying
> using executables built with ocamlopt is of course trivial as they have no
> dependencies beyond any libraries you choose to use.
>
> Partly because of how long I've used OCaml, I still build it from sources
> - but there are now several options including the packaged Windows
> installer, GODI/WODI, etc. Although Windows OCaml users are a minority,
> there are quite a few developers actively contributing (the recent 64-bit
> MinGW port was community-initiated, I think).
>
> Last time I looked, Windows support for opam appeared to be a todo list
> item, but I haven't looked in a while (laziness... I already have parallel
> build scripts of my own, so a package manager is lower down my priority
> list)
>
> HTH,
>
>
> David
>
[-- Attachment #2: Type: text/html, Size: 2490 bytes --]
next prev parent reply other threads:[~2013-06-24 10:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 9:07 Bikal Gurung
[not found] ` <E51C5B015DBD1348A1D85763337FB6D9CC8677FE@Remus.metastack.local>
2013-06-24 10:01 ` Bikal Gurung [this message]
2013-06-24 10:11 ` Jonathan Protzenko
2013-06-24 12:10 ` Malcolm Matalka
2013-06-24 17:18 ` Adrien Nader
2013-06-25 8:40 ` David Allsopp
2013-06-26 18:17 ` Adrien Nader
2013-06-26 19:55 ` David Allsopp
2013-06-24 17:21 ` Adrien Nader
2013-06-24 20:16 ` AW: " Gerd Stolpmann
2013-06-26 18:29 ` Adrien Nader
2013-06-26 18:46 ` Wojciech Meyer
[not found] <20130626113838.0643281793@sympa.inria.fr>
2013-06-26 12:02 ` r.3
2013-06-26 17:45 ` Bikal Gurung
2013-06-26 17:55 ` David Allsopp
2013-06-26 18:07 ` Bikal Gurung
2013-06-26 18:28 ` Wojciech Meyer
2013-06-26 18:12 ` Adrien Nader
2013-06-26 19:54 ` 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=CAB-rfD0vdWWtvVaBsJoXJeU63EXhuyAK-j6mifW8h9E4spB-Uw@mail.gmail.com \
--to=bikal.gurung@lemaetech.co.uk \
--cc=caml-list@inria.fr \
--cc=dra-news@metastack.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