caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Matt Gushee <matt@gushee.net>
To: caml-list@inria.fr
Subject: Re: [Caml-list] GODI news
Date: Sat, 9 Aug 2003 11:05:50 -0600	[thread overview]
Message-ID: <20030809170549.GH21525@swordfish> (raw)
In-Reply-To: <1060419878.988.36.camel@ice.gerd-stolpmann.de>

On Sat, Aug 09, 2003 at 11:04:38AM +0200, Gerd Stolpmann wrote:
> > 
> > Why Cygwin, rather than MinGW?
> > 
> Simple answer: It is unwise to do the second step before the first.
> Using Cygwin means that you have a full POSIX environment (Unix tools,
> libraries), but there are already typical Windows problems, e.g.
> filename conventions, CRLF, etc. Solve these first!

Okay. I trust that you know what you are talking about, but I still
don't really understand. By saying "there are already ..." are you
implying that the "typical Windows problems" become worse when using
MinGW? And further, are these problems that can actually be solved,
or simply worked around.

> For the build environment, it is unlikely that we ever get rid of
> Cygwin.

I thought that MinGW came with gcc, gnu make, and so on. Am I mistaken,
or are they poorly implemented, or what?

-- 
Matt Gushee                 When a nation follows the Way,
Englewood, Colorado, USA    Horses bear manure through
mgushee@havenrock.com           its fields;
http://www.havenrock.com/   When a nation ignores the Way,
                            Horses bear soldiers through
                                its streets.
                                
                            --Lao Tzu (Peter Merel, trans.)

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  reply	other threads:[~2003-08-09 17:06 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-08 21:20 Gerd Stolpmann
2003-08-08 21:37 ` Matt Gushee
2003-08-09  9:04   ` Gerd Stolpmann
2003-08-09 17:05     ` Matt Gushee [this message]
2003-08-09 18:06       ` Dmitry Bely
2003-08-09 18:44         ` Alexander V. Voinov
2003-08-09 21:16           ` Sven Luther
2003-08-10  1:11             ` skaller
2003-08-10  7:35               ` Sven Luther
2003-08-10 20:25                 ` skaller
2003-11-05 21:28 [Caml-list] GODI News Gerd Stolpmann
2003-11-05 22:59 ` Ken Rose
2003-12-02 22:35 [Caml-list] GODI news Gerd Stolpmann
2003-12-02 23:09 ` Alain.Frisch
2003-12-02 23:36   ` Benjamin Geer
2003-12-02 23:51     ` Alain.Frisch
2003-12-03  5:12     ` William Lovas
2003-12-03 11:16       ` Sven Luther
2003-12-04  4:25         ` William Lovas
2003-12-08 12:44           ` Sven Luther
2003-12-03 21:14       ` Sylvain LE GALL
2003-12-03 23:59     ` Gerd Stolpmann
2003-12-04  0:41       ` Benjamin Geer
2003-12-05 21:23         ` Gerd Stolpmann
2003-12-03  7:49 ` Byron Hale
2004-01-04 21:12 Gerd Stolpmann
2004-02-27  9:41 Gerd Stolpmann
2004-04-28 12:38 Gerd Stolpmann
2004-05-14 16:29 Gerd Stolpmann
2012-10-22  2:39 Gerd Stolpmann

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=20030809170549.GH21525@swordfish \
    --to=matt@gushee.net \
    --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;
as well as URLs for NNTP newsgroup(s).