Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Bernd Bunk <bernd.bunk@intel.com>
Cc: tromey@redhat.com, palves@redhat.com, gdb-patches@sourceware.org,
	bernd.bunk@intel.com
Subject: Re: [PATCH v2] Added file properties to windows gdb executable for all mingw32 builds.
Date: Thu, 22 Aug 2013 15:09:00 -0000	[thread overview]
Message-ID: <8361uxkbi9.fsf@gnu.org> (raw)
In-Reply-To: <1377161766-8318-1-git-send-email-bernd.bunk@intel.com>

> From: Bernd Bunk <bernd.bunk@intel.com>
> Cc: gdb-patches@sourceware.org, Bernd Bunk <bernd.bunk@intel.com>
> Date: Thu, 22 Aug 2013 10:56:06 +0200
> 
> On Windows OS it is customary that executables and DLL's show file properties.
> These contain product name/version, file name/version, company/copyright info.
> File properties are visible by right-click on the file, selecting properties \ details.
> This patch adds file properties to the gdb executable for all mingw builds.

Thanks, this looks OK to me, except for a couple of comments:

> 	* Makefile.in (win_exe_properties.h): Add rule to create
> 	win_exe_properties.h header file with file property information.
> 	(win_exe_properties.o): Added rule to build the resource file.
> 	* configure: Add win_exe_properties.o to mingw32 specific
> 	objects.
> 	* common/create-win_exe_properties.sh: Shell script to
> 	create a win_exe_properties.h header file containing all
> 	information/defines for the gdb executable file properties.
> 	New file.
> 	* win_exe_properties.rc: Resource file implementing
> 	gdb executable file properties for windows/mingw32 builds.
> 	It includes auto-generated win_exe_properties.h file with
> 	property information. New file.

New files you add should say "New file".  Also, please leave two
spaces between sentences, the US style.

The GNU project doesn't like calling Windows a "win", so I suggest to
rename the files and the script to use something like mingw instead.

> +# 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?
> +#include "afxres.h"

Is this header really needed?

Thanks.


  reply	other threads:[~2013-08-22 15: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 [this message]
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
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=8361uxkbi9.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