public inbox for
help / color / mirror / Atom feed
Subject: insight/169: tk.ico used instead of gdbtool.ico when building under Cygwin
Date: Tue, 09 Jul 2002 08:33:00 -0000	[thread overview]
Message-ID: <> (raw)

>Number:         169
>Category:       insight
>Synopsis:       tk.ico used instead of gdbtool.ico when building under Cygwin
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Jul 09 08:33:01 PDT 2002
>Originator:     Martin J. O'Riordan,  Silaria Ltd., Dublin, Ireland
>Release:        insight-5.1 and insight-5.2
Windows 2000 Professional
Cygwin - latest as of 7 July 2002
I have ported the Gnu development tools including Insight to our processor, and I had noticed that in Insight 5.1, the icon in the top left corner of each window displayed the Cygnus icon (cygnus.ico) instead of the expected 'gdbtool.ico'.  When I moved to Insight-5.2, I noticed that this changed to the Tk icon 'tk.ico'.  The reason for this is that the Windows resource files 'tk*.ico' now refer to 'tk.ico' instead of 'cygnus.ico'.

Either way, they should be referring to the GDBTK icon 'gdbtool.ico'.

The reason this seems to be the case, is that the resource files for Tk contain a definition for many symbols other than "tk", whereas 'gdb.rc' only defines "tk".  The linker overrides the "gdbres.o" definition and the intended icon is not correctly bound.
Build GDB-Insight 5.2 for a cross development target under Windows 2000 Professional using Cygwin.  Run this version of GDB and notice the icon on the title bar is not the expected one.
I think that the Tk resources need to be broken out into separate files so that the "tk" icon is on its own in a separate '.o' file.  However, I do not understand the Tk library well enough to be confident about this.

             reply	other threads:[~2002-07-09 15:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-09  8:33 martin.oriordan [this message]
2002-11-19 20:22 kseitz

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).