From: "Bunk, Bernd" <bernd.bunk@intel.com>
To: Pedro Alves <palves@redhat.com>, Eli Zaretskii <eliz@gnu.org>
Cc: "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: Fri, 23 Aug 2013 14:09:00 -0000 [thread overview]
Message-ID: <E2C54CDFBA86B845B3B075E2B2042A91202566EF@IRSMSX106.ger.corp.intel.com> (raw)
In-Reply-To: <521766B1.6070301@redhat.com>
> -----Original Message-----
> From: Pedro Alves [mailto:palves@redhat.com]
> Sent: Friday, August 23, 2013 3:42 PM
> To: Eli Zaretskii
> Cc: Bunk, Bernd; tromey@redhat.com; gdb-patches@sourceware.org
> Subject: Re: [PATCH v2] Added file properties to windows gdb executable
> for all mingw32 builds.
>
> On 08/23/2013 02:27 PM, Eli Zaretskii wrote:
> >> Date: Fri, 23 Aug 2013 14:06:51 +0100
> >> From: Pedro Alves <palves@redhat.com> Right, I mean, other than the
> >> fact that the patch only enabled this on mingw, there's nothing in
> >> the feature itself that'd prevent it from working on Cygwin, afaik,
> >> as this is a Windows binary thing, not specific of MinGW's
> toolchain.
> >
> > The question is: do the Cygwin maintainers _want_ the Cygwin GDB have
> > all these resources linked into the binary. Cygwin is a Posix
> > environment, where these attributes are neither expected nor (AFAIK)
> > used in any way.
>
> I'm really just pointing out Cygwin as rationale for preferring
> windows-*.c as file name instead of mingw-*. In my mind, given this is
> a Windows/PE feature, not specific of mingw, the file naming would
> reflect that. That is, name the files for what they are, not for how
> they're used today. If the Cygwin guys at some point want to link in
> the resources, then it'd be a no brainer to tweak configure. If the
> files are called mingw-*, then such a change would be kind of awkward
> without a file rename. But this is really bike shedding, not worth
> spending more cycles on it. If you guys prefer mingw, then let's go
> with it.
Ok, I am also fine with windows-*, as long as I am not expected to do this Cygwin adaptation. If they want this feature they will have it easy and they have the means to test it. Perfect for both parties. I will now rework the code according to the feedback from the last discussions.
>
> --
> Pedro Alves
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen, Deutschland
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk
Registergericht: Muenchen HRB 47456
Ust.-IdNr./VAT Registration No.: DE129385895
Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052
next prev parent reply other threads:[~2013-08-23 14:09 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 [this message]
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
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=E2C54CDFBA86B845B3B075E2B2042A91202566EF@IRSMSX106.ger.corp.intel.com \
--to=bernd.bunk@intel.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--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