From: Mark Mitchell <mark@codesourcery.com>
To: Christopher Faylor <me@cgf.cx>
Cc: paul@codesourcery.com, gdb@sourceware.org
Subject: Re: Windows support in GDB
Date: Fri, 29 Apr 2005 16:31:00 -0000 [thread overview]
Message-ID: <42725D6A.7040103@codesourcery.com> (raw)
In-Reply-To: <20050429160040.GH10017@trixie.casa.cgf.cx>
Christopher Faylor wrote:
> While I am the Windows maintainer for gdb, I have been thinking that
> maybe I might have to step down if it means that I'll have to support a
> Windows configuration for which I have little interest.
I think that would be a shame.
> I haven't asked what the problem is with just using cygwin with gdb.
> I suspect that the standard two problems are:
You might ask the MinGW community why they exist. :-)
One reason to use MinGW is that you're using other tools that rely on
Windows paths, and don't understand Cygwin mount points. Or you
yourself don't understand Cygwin mount points. :-)
The fundamental reason for us to use it is that our customers say --
strongly -- that they do not want to use Cygwin. (In contrast, I use
Cygwin every day.) There are a lot of possible reasons for the customer
desire, and it doesn't really seem all that useful to debate the
reasons, as our debate won't change their minds.
--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304
next prev parent reply other threads:[~2005-04-29 16:23 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-29 15:32 Mark Kettenis
2005-04-29 15:32 ` Daniel Jacobowitz
2005-04-29 16:08 ` Christopher Faylor
2005-04-29 16:31 ` Mark Mitchell [this message]
2005-04-29 16:36 ` Christopher Faylor
2005-04-29 16:47 ` Mark Mitchell
2005-04-29 16:56 ` Christopher Faylor
2005-04-29 17:05 ` Mark Mitchell
2005-04-29 17:16 ` Christopher Faylor
2005-05-01 20:13 ` Eli Zaretskii
2005-05-01 19:50 ` Eli Zaretskii
2005-04-29 16:52 ` Dave Korn
2005-04-29 16:57 ` Mark Mitchell
2005-04-29 17:00 ` Dave Korn
2005-04-30 16:18 ` Mark Kettenis
2005-04-30 20:37 ` Christopher Faylor
2005-05-01 20:05 ` Eli Zaretskii
2005-05-01 20:06 ` Mark Mitchell
2005-05-01 20:24 ` Eli Zaretskii
2005-04-29 16:32 ` Kris Warkentin
2005-04-29 16:40 ` Christopher Faylor
2005-04-29 17:00 ` Kris Warkentin
2005-05-01 19:55 ` Eli Zaretskii
2005-05-01 21:41 ` Christopher Faylor
2005-05-02 19:03 ` Eli Zaretskii
2005-05-02 19:56 ` Christopher Faylor
2005-04-29 16:48 ` Daniel Jacobowitz
2005-04-29 17:33 ` Christopher Faylor
2005-04-29 17:58 ` Daniel Jacobowitz
2005-04-29 19:08 ` Christopher Faylor
2005-04-29 19:36 ` Daniel Jacobowitz
2005-04-29 22:01 ` Christopher Faylor
2005-05-02 15:41 ` Andrew Cagney
2005-05-02 15:45 ` Daniel Jacobowitz
2005-04-29 16:04 ` Kris Warkentin
2005-04-29 16:23 ` Mark Mitchell
2005-04-29 16:46 ` Christopher Faylor
2005-04-29 16:50 ` Mark Mitchell
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=42725D6A.7040103@codesourcery.com \
--to=mark@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=me@cgf.cx \
--cc=paul@codesourcery.com \
/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