Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Christopher Faylor <me@cgf.cx>
To: Mark Mitchell <mark@codesourcery.com>,
	gdb-patches@sources.redhat.com, Eli Zaretskii <eliz@gnu.org>
Subject: Re: MinGW build instructions
Date: Wed, 11 May 2005 18:45:00 -0000	[thread overview]
Message-ID: <20050511161153.GH10119@trixie.casa.cgf.cx> (raw)
In-Reply-To: <4281B26C.60208@codesourcery.com>

On Wed, May 11, 2005 at 12:21:16AM -0700, Mark Mitchell wrote:
>Eli Zaretskii wrote:
>>As an aside, what little experience I have in porting Unix programs to
>>MinGW tells me that setting up an environment to build a package is
>>not a trivial job.  There are issues with what shell to use and how to
>>set it up, what ports of auxiliary tools (Coreutils, Grep, Awk, etc.)
>>to use and how to set them up, what non-default libraries to install
>>and link against (the MinGW libraries such as libiberty, Libgw32c), etc.
>>
>>So perhaps, if we are going to have an alive MinGW port, it is a good
>>idea to have a README.MinGW file in the distro that would describe how
>>to build such a port of GDB.  A description of the setup Mark uses to
>>work on the port would be a good starting point.
>
>I'd be happy to write it up -- but what I do is simple: I cheat.  I use 
>cross compilers from i686-pc-linux-gnu to i686-ming32.  If it would be 
>useful for me to show how I configure and build GDB like that, I'm happy 
>to write that up; just let me know.

Some people use the cygwin-fork (grr...) MSYS to do mingw development.
It should contain every package that you need to build gdb, I think.
And, I am mentioning this through gritted teeth in the interests of
full disclosure.

At least one of the mingw developers just uses cygwin to do mingw
development, which, of course, seems to be to be the ultimate solution
if you want to work on windows.  AFAIK, cygwin's libraries like autoconf
and gettext seem to be updated more frequently than MSYS.

You don't have to install 700MB of cygwin to get things working.  You
should be able to get away with just installing the bits that you need +
the mingw compiler.  Or, it is possible that a i686-pc-mingw32-gcc
wrapper like:

#!/bin/sh
exec gcc -mno-cygwin "$@"

may "just work" with the cygwin version of gcc.  The -mno-cygwin option
to gcc actually uses the mingw headers and libraries.  Unfortunately,
there is a problem with cygwin-bleedover for libraries, though, so
you have to be careful not to specify any libraries on the command
line which exist on cygwin but not in mingw.  This is something that
I keep meaning to fix in gcc/binutils...

cgf


  parent reply	other threads:[~2005-05-11 16:12 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-09 20:42 PATCH: Use getche on Win32 Mark Mitchell
2005-05-10  6:01 ` Eli Zaretskii
2005-05-10 11:45   ` Mark Mitchell
2005-05-10 20:05     ` Eli Zaretskii
2005-05-10 20:26       ` Mark Mitchell
2005-05-10 20:31         ` Eli Zaretskii
2005-05-10 20:49           ` Daniel Jacobowitz
2005-05-10 21:41             ` Christopher Faylor
2005-05-11  6:55               ` Christopher Faylor
2005-05-11  7:13                 ` Eli Zaretskii
2005-05-11  7:17                   ` Mark Mitchell
2005-05-11  7:21                 ` MinGW build instructions (was: PATCH: Use getche on Win32) Eli Zaretskii
2005-05-11  7:29                   ` MinGW build instructions Mark Mitchell
2005-05-11  7:53                     ` Eli Zaretskii
2005-05-11 18:45                     ` Christopher Faylor [this message]
2005-05-11 19:05                       ` Eli Zaretskii
2005-05-11 19:58                         ` Christopher Faylor
2005-05-11 23:16                           ` Eli Zaretskii
2005-05-11  6:56             ` PATCH: Use getche on Win32 Mark Mitchell
2005-05-11 13:42               ` Eli Zaretskii
2005-05-13 11:42                 ` Mark Mitchell
2005-05-13 15:18                   ` Eli Zaretskii
2005-05-11  7:07             ` Eli Zaretskii

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=20050511161153.GH10119@trixie.casa.cgf.cx \
    --to=me@cgf.cx \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mark@codesourcery.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