Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Kuba Ober <ober.14@osu.edu>
To: caml-list@yquem.inria.fr
Subject: Re: Re : Re: [Caml-list] Re: MinGW port w/o Cygwin?
Date: Wed, 26 Dec 2007 12:59:30 -0500	[thread overview]
Message-ID: <200712261259.31076.ober.14@osu.edu> (raw)
In-Reply-To: <90823c940712240450m6ade7eb9h5f2948f3c0f91fb1@mail.gmail.com>

On Monday 24 December 2007, Dmitry Bely wrote:
> On Dec 23, 2007 7:33 PM, Adrien <camaradetux@gmail.com> wrote:
> > > I guess that Ocaml maintainers should just drop that Cygwin
> > > requirement, and tweak their build process to work "out of the box"
> > > with MSYS/MinGW.
> >
> > You shouldn't see cygwin as a _requirement_.
> > Ocaml installation from source (let the binary distributions be a
> > special case) use C. If there is no c compiler installed as it is
> > under all windows installations (I mean right after setup is
> > completed) ocaml simply can't be installed ; the problem is not with
> > ocaml or cygwin but with windows. Cygwin is not a fancy requirement
> > just one of the few ways to get a c compiler under windows.
>
> Not only compiler; Ocaml build process actively uses various Unix
> utilities that Cygwin provides: make, sh, sed, etc. I see no reason to
> have another set of there utilities in addition to Cygwin's one.

Because this really mixes things up. The Ocaml build environment becomes very 
different from Ocaml execution environment. To a point where if, say, Ocaml's 
build process would use Ocaml at a late point in the process, you'd need two 
Ocaml builds: one native, one cygwin-based. The native one wouldn't dig any 
cygwin paths for example, yet would be what you want to use if you were to 
distribute Ocaml with your commercial application, for example.

Basically, at this point Ocaml is very Windows-unfriendly because of this 
attitude. For a good example of how it shuld work/look, see Trolltech's Qt, 
whose build process works just fine on Windows without bringing in Cygwin or 
even MSYS. It runs using various VC versions, as well as Mingw.

Cheers, Kuba


  reply	other threads:[~2007-12-26 17:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-20 14:30 Kuba Ober
2007-12-20 15:23 ` Zheng Li
2007-12-20 20:18   ` [Caml-list] " Kuba Ober
2007-12-21 14:06     ` Dmitry Bely
2007-12-23 15:20       ` "Márk S. Zoltán"
2007-12-23 16:33         ` Re : " Adrien
2007-12-24 12:50           ` Dmitry Bely
2007-12-26 17:59             ` Kuba Ober [this message]
2007-12-26 17:54           ` Kuba Ober
2008-01-06 15:14             ` Re : " Adrien
2008-01-08 14:25               ` Kuba Ober
2007-12-24 10:40         ` Richard Jones
2007-12-26 18:01           ` Kuba Ober
2007-12-26 17:45       ` Kuba Ober
2007-12-26 22:48         ` Dmitry Bely
2007-12-27 12:41           ` Kuba Ober

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=200712261259.31076.ober.14@osu.edu \
    --to=ober.14@osu.edu \
    --cc=caml-list@yquem.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