From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: Allow building GDB with Python support on Windows/MinGW
Date: Sat, 22 Jan 2011 23:45:00 -0000 [thread overview]
Message-ID: <1295739863-1006-1-git-send-email-brobecker@adacore.com> (raw)
This set of patches makes the necessary changes to able to build
GDB with Python support on Windows/MinGW. The patches are a little
different from the first one I posted a few days ago
(http://www.sourceware.org/ml/gdb-patches/2011-01/msg00431.html),
as I went back and forth between several options. But I think
that the current set ended up being the cleanest of al.
This work certained made me raise the question of whether we really
want to support so many ways of building GDB with Python. But that's
for another discussion...
next reply other threads:[~2011-01-22 23:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-22 23:45 Joel Brobecker [this message]
2011-01-22 23:45 ` [RFA 2/2] allow building GDB with Python support on MinGW Joel Brobecker
2011-01-28 11:32 ` Tom Tromey
2011-01-31 4:50 ` Joel Brobecker
2011-01-23 0:14 ` [RFA 1/2] do not use python<version> subdir when including Python .h file Joel Brobecker
2011-01-28 11:24 ` Tom Tromey
2011-01-28 14:37 ` Joel Brobecker
2011-01-28 14:54 ` Tom Tromey
2011-01-31 4:44 ` Joel Brobecker
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=1295739863-1006-1-git-send-email-brobecker@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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