Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Dave Murphy <wintermute2k4@ntlworld.com>
To: Steve Folly <gdb-list@spfweb.co.uk>
Cc: GDB List <gdb@sources.redhat.com>
Subject: Re: Can't build gdb for mingw32 if not native? :-(
Date: Thu, 29 Sep 2005 09:01:00 -0000	[thread overview]
Message-ID: <433BAD46.2020006@ntlworld.com> (raw)
In-Reply-To: <AD89E4BF-E8D5-4D3E-9061-A74544D9BAD0@spfweb.co.uk>

Steve Folly wrote:

>
> Some of our apps run full screen and having a remote machine to debug  
> on helps quite a bit.
>
> I guess dual-screen capable PCs will help here, but our current  
> hardware (supplied by our customer) doesn't support that.
>
I'm nearly sure that remote debugging has been done using mingw tools 
although I could be mistaken. It's probably worth asking on the mingw 
mailing lists about this.

>
> I think Cygwin may be the way to go - some makefiles we have running  
> on OS X are using utilities like sed and grep, and we'd like to port  
> them to Windows with the minimum of fuss.
>
>
Msys provides much of what you need for comfortable use of unix style 
tools, the basic install definitely includes sed and grep. I build gnu 
tools with mingw/msys on a regular basis, including gcc cross compilers.

http://www.mingw.org/

This wiki page also provides some useful information on building a cross 
compiler in that environment.

http://www.mingw.org/MinGWiki/index.php/mingw%20hosted%20cross%20compiler

Dave



      parent reply	other threads:[~2005-09-29  9:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-27 21:11 Steve Folly
2005-09-27 21:12 ` Steve Folly
2005-09-27 21:18   ` Daniel Jacobowitz
2005-09-27 21:54     ` Steve Folly
2005-09-27 22:26       ` Daniel Jacobowitz
2005-09-28 11:52       ` Andrew STUBBS
2005-09-28 20:08         ` Steve Folly
2005-09-28 21:21           ` Eli Zaretskii
2005-09-29  0:41             ` Christopher Faylor
2005-09-29  9:01           ` Dave Murphy [this message]

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=433BAD46.2020006@ntlworld.com \
    --to=wintermute2k4@ntlworld.com \
    --cc=gdb-list@spfweb.co.uk \
    --cc=gdb@sources.redhat.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