This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v2] Added file properties to windows gdb executable for all mingw32 builds.
- From: Pedro Alves <palves at redhat dot com>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: bernd dot bunk at intel dot com, tromey at redhat dot com, gdb-patches at sourceware dot org
- Date: Fri, 23 Aug 2013 14:42:09 +0100
- Subject: Re: [PATCH v2] Added file properties to windows gdb executable for all mingw32 builds.
- References: <1377161766-8318-1-git-send-email-bernd dot bunk at intel dot com> <8361uxkbi9 dot fsf at gnu dot org> <52166564 dot 90605 at redhat dot com> <83wqndijp0 dot fsf at gnu dot org> <52175E6B dot 8080703 at redhat dot com> <83haegilk1 dot fsf at gnu dot org>
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.
--
Pedro Alves