Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Bunk, Bernd" <bernd.bunk@intel.com>
Cc: tromey@redhat.com, palves@redhat.com, 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:37:00 -0000	[thread overview]
Message-ID: <83eh9kiic8.fsf@gnu.org> (raw)
In-Reply-To: <E2C54CDFBA86B845B3B075E2B2042A91202566CA@IRSMSX106.ger.corp.intel.com>

> From: "Bunk, Bernd" <bernd.bunk@intel.com>
> CC: "tromey@redhat.com" <tromey@redhat.com>, "palves@redhat.com"
> 	<palves@redhat.com>, "gdb-patches@sourceware.org"
> 	<gdb-patches@sourceware.org>
> Date: Fri, 23 Aug 2013 13:44:58 +0000
> 
> > > +# check for environment variables to replace certain file properties
> > > +[ -n "$WIN_EXE_VERSION" ] && version=$WIN_EXE_VERSION [ -n
> > > +"$WIN_EXE_COMPANY_NAME" ] && company_name=$WIN_EXE_COMPANY_NAME
> > > +[ -n "$WIN_EXE_FILE_DESCRIPTION" ] &&
> > > +file_description=$WIN_EXE_FILE_DESCRIPTION
> > > +[ -n "$WIN_EXE_PRODUCT_NAME" ] && product_name=$WIN_EXE_PRODUCT_NAME
> > > +[ -n "$WIN_EXE_INTERNAL_NAME" ] &&
> > > +internal_name=$WIN_EXE_INTERNAL_NAME
> > > +[ -n "$WIN_EXE_ORIGINAL_FILENAME" ] &&
> > > +original_filename=$WIN_EXE_ORIGINAL_FILENAME
> > > +[ -n "$WIN_EXE_COPYRIGHT" ] && copyright=$WIN_EXE_COPYRIGHT [ -n
> > > +"$WIN_EXE_LICENSE" ] && license=$WIN_EXE_LICENSE [ -n
> > > +"$WIN_EXE_CONFIGURED" ] && configured=$WIN_EXE_CONFIGURED [ -n
> > > +"$WIN_EXE_SUPPORT" ] && support=$WIN_EXE_SUPPORT
> > 
> > This looks like unnecessary featurism to me.  Is it really needed, and
> > if so, in what use cases?
> Yes, it is needed. Not in here, but for every company which changes/adds and re-distributes gdb.
> I started this feature because our Product Validation does not like binaries without legal information.
> And off course this is different depending on who ships the product.
> Without a way to change the strings the complete changeset would be useless for me.

You can always modify the source of these attributes, can't you?  It's
not like you change these strings several times a day, right?

> > > +#include "afxres.h"
> > 
> > Is this header really needed?
> Yes, unfortunately.
> This header file "implements" the resource language used below in the RC file.

Sorry, I don't understand: this header file in MinGW distribution just
includes windows.h, defines IDC_STATIC, and that's it.  What do you
have in it?


  parent reply	other threads:[~2013-08-23 14:37 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
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 [this message]
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=83eh9kiic8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=bernd.bunk@intel.com \
    --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