From: David Allsopp <dra-news@metastack.com>
To: "OCaml List (caml-list@inria.fr)" <caml-list@inria.fr>
Subject: RE: [Caml-list] Ocaml on windows
Date: Wed, 26 Jun 2013 19:55:38 +0000 [thread overview]
Message-ID: <E51C5B015DBD1348A1D85763337FB6D9CC8726CB@Remus.metastack.local> (raw)
In-Reply-To: <20130626181736.GB31557@notk.org>
Adrien Nader wrote:
> On Tue, Jun 25, 2013, David Allsopp wrote:
> > Bikal Gurung wrote:
> > > 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.
> >
> > I meant I use the MinGW port of the compiler rather than the MSVC port -
> I compile it using the mingw-w64 compilers provided with Cygwin. I only
> use Cygwin to compile OCaml and related libraries (again, principally for
> historical reasons, I develop using a normal command shell with GnuWin32
> to provide Unix commands). Building using Cygwin (i.e. the supported way)
> has the benefit that when you get stuck, others are likely to (be able to)
> help! :o) Do you have a particular to want to use MSYS rather than Cygwin?
>
> By the way, wtch out for GnuWin32. It advertises a very broad support but
> it's getting old and most importantly, it lies on several things.
> For instance, fork() is implemented as:
> int fork(void) {
> return -1;
> }
Oh, yes - I know it's limited! But when working from cmd, it's still slightly better than the alternatives at the moment. It's rare that something doesn't work to the point where I need to open a Cygwin terminal (regularly using make, sed, grep, m4, etc. without problem)
> > > 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?
> >
> > Yes. Because I use GnuWin32 (which has its bin folder in my PATH) I
> prefer not to put C:\cygwin\bin in my PATH but symlink through the
> required utilities in C:\Dev\OCaml\bin (C:\Dev\OCaml is my installation
> root for OCaml) - my OCaml installation requires bash.exe (for
> ocamlbuild), cpp.exe (for ocamlnet) and i686-w64-mingw32-ar.exe + i686-
> w64-mingw32-as.exe + i686-w64-mingw32-dlltool.exe + i686-w64-mingw32-
> gcc.exe + i686-w64-mingw32-ranlib.exe for ocamlopt.
>
> Do you mean you use gnuwin32's bash.exe for ocamlbuild?
No - that's done using Cygwin's. I actually don't have GnuWin32's bash (or sh) installed.
David
next prev parent reply other threads:[~2013-06-26 19:55 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
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 [this message]
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=E51C5B015DBD1348A1D85763337FB6D9CC8726CB@Remus.metastack.local \
--to=dra-news@metastack.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