From: asmwarrior <asmwarrior@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb@sourceware.org
Subject: Re: Windows build cookbook
Date: Sun, 31 Jul 2011 02:18:00 -0000 [thread overview]
Message-ID: <4E34BBCE.4040700@gmail.com> (raw)
In-Reply-To: <m3livj8wyf.fsf@fleche.redhat.com>
On 2011-7-28 1:17, Tom Tromey wrote:
> Eli> Thanks. That's not Windows-specific, so I guess there are no
> Eli> Windows-specific issues here?
>
> I would venture to guess that this is just because nobody has written
> the text for the manual, rather than that there are no issues building
> on Windows.
>
> Tom
>
we have create some pages in
http://code.google.com/p/qp-gcc/wiki/build_gdb_msys_en (English version)
and
http://code.google.com/p/qp-gcc/wiki/build_gdb_msys_cn (Chinese version)
Also, the cross build mingw gdb from linux:
http://code.google.com/p/qp-gcc/wiki/CrossbuildGDB
also, the official Mingw page:
http://sourceforge.net/projects/mingw/files/MinGW/BaseSystem/GDB/GDB-7.2/
which contains an instructions to build gdb 7.2 under MSYS.
As a conclusion, no much difficult to build mingw gdb.
asmwarrior
ollydbg from codeblocks' forum
next prev parent reply other threads:[~2011-07-31 2:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 16:03 Eli Zaretskii
2011-07-27 16:07 ` Joel Brobecker
2011-07-27 16:27 ` Eli Zaretskii
2011-07-27 16:37 ` Joel Brobecker
2011-07-27 16:39 ` Joel Brobecker
2011-07-27 17:12 ` Eli Zaretskii
2011-07-27 18:06 ` Kai Tietz
2011-07-27 16:44 ` Tom Tromey
2011-07-27 17:13 ` Eli Zaretskii
2011-07-27 17:17 ` Tom Tromey
2011-07-31 2:18 ` asmwarrior [this message]
2011-07-31 7:54 ` Eli Zaretskii
2011-07-31 12:34 ` asmwarrior
2011-07-31 15:46 ` Eli Zaretskii
2011-07-31 15:54 ` Eli Zaretskii
2011-07-31 20:11 ` Petr Hluzín
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=4E34BBCE.4040700@gmail.com \
--to=asmwarrior@gmail.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=tromey@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