From: Keith Seitz <keiths@cygnus.com>
To: Insight Maling List <insight@sources.redhat.com>
Subject: [PATCH/hack] Running from build dir again
Date: Wed, 19 Sep 2001 11:09:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.33.0109191107370.9780-100000@makita.cygnus.com> (raw)
Hi,
This gross hack allows insight to run from the build directory again.
Recent Tcl/Tk churn has broken this convenience, and, well, as hacky and
ugly as this is, it fixes it.
Keith
ChangeLog
2001-09-19 Keith Seitz <keiths@redhat.com>
* library/main.tcl: Append iwidgets library path, if needed.
* generic/gdbtk.c (gdbtk_init): Add TCLLIBPATH to iwidgets
package index.
Define IWIDGETS_LIBRARY in interpreter so that we can add
this path to the auto_path at the right time later.
Patch
Index: generic/gdbtk.c
===================================================================
RCS file: /cvs/src/src/gdb/gdbtk/generic/gdbtk.c,v
retrieving revision 1.21
diff -u -p -r1.21 gdbtk.c
--- generic/gdbtk.c 2001/09/10 19:21:47 1.21
+++ generic/gdbtk.c 2001/09/19 17:56:40
@@ -434,7 +434,18 @@ gdbtk_init (argv0)
\
if {![info exists env(GDBTK_LIBRARY)]} {\n\
set env(GDBTK_LIBRARY) [file join $srcDir gdb gdbtk library]\n\
- }\n";
+ }\n\
+\
+ # Append the directory with the itcl pkg index\n\
+ if {[info exists env(TCLLIBPATH)]} {\n\
+ append env(TCLLIBPATH) :[file joing $srcDir itcl]\n\
+ } else {\n\
+ set env(TCLLIBPATH) [file join $srcDir itcl]\n\
+ }\n\
+\
+ # We also need to append the iwidgets library path.\n\
+ # Unfortunately, there is no IWIDGETS_LIBRARY.\n\
+ set IWIDGETS_LIBRARY [file join $srcDir itcl iwidgets3.0.0 generic]\n";
Tcl_Obj *commandObj;
Index: library/main.tcl
===================================================================
RCS file: /cvs/src/src/gdb/gdbtk/library/main.tcl,v
retrieving revision 1.4
diff -u -p -r1.4 main.tcl
--- library/main.tcl 2001/09/10 19:21:47 1.4
+++ library/main.tcl 2001/09/19 17:56:56
@@ -58,6 +58,11 @@ namespace import itcl::*
namespace import debug::*
+# Setup iwidgets path, if needed
+if {[info exists IWIDGETS_LIBRARY]} {
+ lappend auto_path $IWIDGETS_LIBRARY
+}
+
if {[catch {package require Iwidgets 3.0} errMsg]} {
set msg "Could not find the Iwidgets libraries.\n\nGot nameofexec: [info nameofexecutable]\nError(s) were: \n$errMsg"
next reply other threads:[~2001-09-19 11:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-19 11:09 Keith Seitz [this message]
2001-09-19 12:03 ` Ian Roxborough
2001-09-19 12:08 ` Keith Seitz
2001-09-19 12:28 ` Ian Roxborough
2001-09-20 10:57 ` Martin M. Hunt
2001-09-20 11:01 ` Keith Seitz
2001-09-20 11:28 ` Ian Roxborough
2001-09-20 11:31 ` Keith Seitz
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=Pine.GSO.4.33.0109191107370.9780-100000@makita.cygnus.com \
--to=keiths@cygnus.com \
--cc=insight@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).