From: Pedro Alves <palves@redhat.com>
To: "Bunk, Bernd" <bernd.bunk@intel.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
"tromey@redhat.com" <tromey@redhat.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2] Added file properties to windows gdb executable for all mingw32 builds.
Date: Mon, 26 Aug 2013 15:42:00 -0000 [thread overview]
Message-ID: <521B6D7D.6080406@redhat.com> (raw)
In-Reply-To: <E2C54CDFBA86B845B3B075E2B2042A9120256D16@IRSMSX106.ger.corp.intel.com>
On 08/26/2013 01:01 PM, Bunk, Bernd wrote:
>> From: Pedro Alves [mailto:palves@redhat.com]
>>>> See gdb/configure.ac, gdb/Makefile.in and gdbtk/gdb.rc etc.
>>>> Isn't this going to conflict on gdbtk builds?
>>> See above, yes it would.
>>
>> Well, it just looks to me that the gdbres.rc resource and the icon are
>> presently only used on Cygwin-hosts builds, because nobody bothered to
>> tweak that configure bit to make it work on mingw-hosts too. That bit
>> is there since at least 2000, and I believe MinGW host support came in
>> much after. Cygwin wanting pretty icons, but MinGW not is kind of
>> strange, wouldn't you say? :-)
>>
>> Do you have any hint at what one would need to do, if one were to
>> enable that icon resource on mingw too?
> I can offer to merge this icon into my mingw rc file in a later checkin.
Thanks. Note the icon should probably only be used for gdbtk/insight
builds, not plain command line gdb builds, and should probably stay in
the gdbtk/ dir. If it's possible to link in more than one rc file,
than there'd be no problem. But if that's not possible, then we'd
need something more magical...
But tbh I cannot even find the sources (icon or gdbtk folder). Someone checked in build rules for something that is not on the same branch (upstream/master). I am new to this gdb coding, but I would never do something like this...
The gdbtk/ directory is part of insight, which (currently) lives in
the same repository but in a different cvs module. You'll need to
"cvs ... co insight" instead of "cvs ... co gdb" to get it.
--
Pedro Alves
next prev parent reply other threads:[~2013-08-26 15:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 8:56 Bernd Bunk
2013-08-22 15:09 ` Eli Zaretskii
2013-08-22 19:24 ` Pedro Alves
2013-08-22 19:55 ` Eli Zaretskii
2013-08-23 13:06 ` Pedro Alves
2013-08-23 13:27 ` Eli Zaretskii
2013-08-23 13:42 ` Pedro Alves
2013-08-23 14:09 ` Bunk, Bernd
2013-08-23 14:07 ` Bunk, Bernd
2013-08-23 14:38 ` Pedro Alves
2013-08-26 12:02 ` Bunk, Bernd
2013-08-26 15:42 ` Pedro Alves [this message]
2013-08-23 13:45 ` Bunk, Bernd
2013-08-23 14:20 ` asmwarrior
2013-08-23 14:56 ` Bunk, Bernd
2013-08-23 14:37 ` Eli Zaretskii
2013-08-26 12:25 ` Bunk, Bernd
2013-08-26 15:24 ` Pedro Alves
2013-08-26 12:34 ` Bunk, Bernd
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=521B6D7D.6080406@redhat.com \
--to=palves@redhat.com \
--cc=bernd.bunk@intel.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@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