Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: Windows build cookbook
Date: Wed, 27 Jul 2011 16:27:00 -0000	[thread overview]
Message-ID: <83tya7elkc.fsf@gnu.org> (raw)
In-Reply-To: <20110727160648.GP1988@adacore.com>

> Date: Wed, 27 Jul 2011 09:06:48 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb@sourceware.org
> 
> > If there's no such thing, could someone who regularly builds the
> > native Windows (a.k.a. MinGW) port please share his/her setup?
> 
> I use the cygwin environment with a MinGW compiler, and configure
> using --build=i686-pc-mingw32 (or --build=x86_64-pc-mingw32).
> Using that approach, it pretty much builds out of the box.

Thanks, but that's not what I meant.  I guess I didn't make myself
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?


  reply	other threads:[~2011-07-27 16:27 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 [this message]
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
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=83tya7elkc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --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