From: Kris Warkentin <kewarken@qnx.com>
To: Christopher Faylor <me@cgf.cx>
Cc: mark@codesourcery.com, paul@codesourcery.com, gdb@sourceware.org
Subject: Re: Windows support in GDB
Date: Fri, 29 Apr 2005 16:32:00 -0000 [thread overview]
Message-ID: <42726061.5090101@qnx.com> (raw)
In-Reply-To: <20050429160040.GH10017@trixie.casa.cgf.cx>
Christopher Faylor wrote:
>I haven't asked what the problem is with just using cygwin with gdb.
>I suspect that the standard two problems are:
>
>1) cygwin is "slow" (which really only is an issue for configure/make)
>
>
Actually, my preliminary compilation benchmarks show a 15-20% increase
in compilation speed on MinGW versus Cygwin.
>and
>
>2) You can't trivially include your own version of cygwin1.dll with
>a distribution since it could conflict with a version already on
>the system.
>
3) Paths. This is a HUGE problem because you can't assume that your
Windows customers are interested in using a Unix style of work flow.
MinGW supports regular Windows paths without the whole /cygdrive/
system. If you have a pure Windows app interacting with Cygwin tools
(take Eclipse for example) you wind up putting an awful lot of cruft in
to deal with pathname conversion. You can even get problems when your
debug information in your binary has either Cygwin or Windows paths.
cheers,
Kris
next prev parent reply other threads:[~2005-04-29 16:31 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
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 [this message]
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=42726061.5090101@qnx.com \
--to=kewarken@qnx.com \
--cc=gdb@sourceware.org \
--cc=mark@codesourcery.com \
--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