Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Bernd Bunk <bernd.bunk@intel.com>
Cc: tromey@redhat.com, palves@redhat.com, eliz@gnu.org,
	       gdb-patches@sourceware.org
Subject: Re: [PATCH v3] Added file properties to windows gdb executable for all mingw32 builds.
Date: Fri, 23 Aug 2013 16:01:00 -0000	[thread overview]
Message-ID: <52178748.9070909@redhat.com> (raw)
In-Reply-To: <1377273278-10370-1-git-send-email-bernd.bunk@intel.com>

On 08/23/2013 04:54 PM, Bernd Bunk wrote:
> On Windows OS it is custom 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.
> 
> 2013-08-14  Bernd Bunk  <bernd.bunk@intel.com>
> 
> 	* Makefile.in (windows_exe_properties.h): Add rule to create
> 	windows_exe_properties.h header file with file property information.
> 	(windows_exe_properties.o): Added rule to build the resource file.

I didn't find where this was updated to write to a temporary file, and
then move to the final destination.  Did I miss something?

> 	* configure: Add windows_exe_properties.o to mingw32 specific
> 	objects.

configure is a generated file.  You'll need to edit configure.ac instead.

-- 
Pedro Alves


  reply	other threads:[~2013-08-23 16:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-23 15:55 Bernd Bunk
2013-08-23 16:01 ` Pedro Alves [this message]
2013-08-26 12:27   ` Bunk, Bernd
2013-08-26 12:30   ` Bunk, Bernd
2013-08-26 14:49     ` Pedro Alves
2013-08-23 16:06 ` Pedro Alves
2013-08-26 12:33   ` 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=52178748.9070909@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