From: Kai Tietz <ktietz70@googlemail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sourceware.org
Subject: Re: Windows build cookbook
Date: Wed, 27 Jul 2011 18:06:00 -0000 [thread overview]
Message-ID: <CAEwic4YLGqGiJ277gDLsBsQ0NsMdnLiqy2QqpxDwDY=3DwBO=A@mail.gmail.com> (raw)
In-Reply-To: <20110727163712.GQ1988@adacore.com>
2011/7/27 Joel Brobecker <brobecker@adacore.com>:
>> clear enough. I meant the support packages that GDB needs to be
>> linked against: the Python libraries, termcap/curses, libexpat,
>> readline, libiconv, etc. Which of them do you use? Or do you build
>> them as well by yourself?
>
> - Python: I use the official binaries provided by python.org
> - termcap/curses: Not needed
> - libexpat: I build it (same as GDB)
> - readline: Not needed (included in GDB sources)
> - libiconv: I place the sources in the GDB tree, and it gets
> automatically built. But you could also rebuild it
> yourself.
>
> I think that, apart from Python, it's fairly easy to rebuild your
> dependencies yourself, so that's what we do. However, I do not know
> if the MinGW project provides pre-compiled versions of those packages
> or not.
>
> --
> Joel
Well, build of Windows is mostly OOTB. Most important point is the
libexpat, as without it DLL debugging isn't possible. The rest is
more an issue of pre-installing proper packages. There is not much
magic about building GDB for Windows.
Yes, both mingw.org and mingw-w64 ventures are providing pre-build
version of gdb for users. AFAIR we (mingw-w64) provide even a version
with Python support.
Kai
next prev parent reply other threads:[~2011-07-27 18:06 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 [this message]
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
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='CAEwic4YLGqGiJ277gDLsBsQ0NsMdnLiqy2QqpxDwDY=3DwBO=A@mail.gmail.com' \
--to=ktietz70@googlemail.com \
--cc=eliz@gnu.org \
--cc=gdb@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