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:54:44 -0500 [thread overview]
Message-ID: <200712261254.44486.ober.14@osu.edu> (raw)
In-Reply-To: <666572260712230833j79ea3f41vc3649b6b3e17940f@mail.gmail.com>
On Sunday 23 December 2007, Adrien wrote:
> 2007/12/20, Kuba Ober <ober.14@osu.edu>:
> > 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.
>
> Also mingw without cygwin still lacks a lot of things. Capabilities
> are there but it seems header files have not been updated in ages and
> linker flags need to be different (you will often need -lws2_32 for
> many C apps especially).
THe right way is to update mingw headers, submit to the maintainers, and go
from there. That's the OSS way.
> Anyway, the result is a big headache for the developper. I perfectly
> understand the ocaml team is not willing to make a complete mingw/msys
> port ; it's such a mess.
It's the only sane way to go. THere's no technical reason to require a unix
environment to build ocaml. Big applications build on Windows just fine...
> So there would be msvc, cygwin, cygwin/mingw, msys/mingw with
> different configuration files for each. While such a port would be
> easy to create it wouldn't be wise to create it imho ; it wouldn't
> help maintaining and would create bugs along with more work for the
> ocaml team.
Supporting Cygwin at all is a waste IMHO. Either you run Unix or Windows,
choose one and stick with it...
> And then one could add a SFU port (Services For Unix) which lets you
> compile ocaml without problem except that it works so well ocaml
> thinks it is running under unix and uses forward-slashes as path
> separators. (everything that ./configure can enable is enabled)
IIRC Windows accepts forward slashes everywhere just fine.
> compile with mingw just to remember last time I tried I spent two
> hours. I then used sfu, cd'ed in the source directory, ./configure,
> make, strip and within 90 seconds my rsync build was ready to
> download. SFU is free though not free as in free speech, but when
> you've spent hours on msys/mingw, you can accept anything and be
> really happy with it. *)
Well, all it means is that Ocaml wasn't designed to build on Windows, that's
it. MSYS provides what reasonably can be provided without a Unix emulation
layer. THe fact that Oaml uses a Unix-centric build system and whatnot makes
things the way they are. The windows build could dispense with configure and
whatnot.
Cheers, Kuba
next prev parent reply other threads:[~2007-12-26 17:54 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
2007-12-26 17:54 ` Kuba Ober [this message]
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=200712261254.44486.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