From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.4 required=5.0 tests=AWL,DNS_FROM_RFC_ABUSE autolearn=disabled version=3.1.3 Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by yquem.inria.fr (Postfix) with ESMTP id 2BCBBBC69 for ; Wed, 26 Dec 2007 18:59:39 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Aq4HAG4lckdDWxLC/2dsb2JhbACBV6dp X-IronPort-AV: E=Sophos;i="4.24,209,1196636400"; d="scan'208";a="20705620" Received: from ip67-91-18-194.z18-91-67.customer.algx.net (HELO server1.bertec.net) ([67.91.18.194]) by mail4-smtp-sop.national.inria.fr with ESMTP; 26 Dec 2007 18:59:38 +0100 Received: from kuba.bertec.net (kuba.bertec.net [192.168.2.16]) by server1.bertec.net (Postfix) with ESMTP id D6844CDFB7 for ; Wed, 26 Dec 2007 12:59:37 -0500 (EST) From: Kuba Ober 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 User-Agent: KMail/1.9.6 (enterprise 0.20071123.740460) References: <200712200930.29585.ober.14@osu.edu> <666572260712230833j79ea3f41vc3649b6b3e17940f@mail.gmail.com> <90823c940712240450m6ade7eb9h5f2948f3c0f91fb1@mail.gmail.com> In-Reply-To: <90823c940712240450m6ade7eb9h5f2948f3c0f91fb1@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200712261259.31076.ober.14@osu.edu> X-Spam: no; 0.00; mingw:01 cygwin:01 ocaml:01 cygwin:01 mingw:01 ocaml:01 compiler:01 compiler:01 ocaml's:01 cheers:01 2007,:98 23,:98 attitude:98 wrote:01 wrote:01 On Monday 24 December 2007, Dmitry Bely wrote: > On Dec 23, 2007 7:33 PM, Adrien 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