Re: Tcl/Tk 8.3 upgrade...

[Mo DeJong <mdejong at cygnus dot com>]

On Thu, 14 Jun 2001, Ian Roxborough wrote:

> On Thu, 14 Jun 2001 08:27:52 -0700 (PDT) Keith Seitz <keiths@cygnus.com> wrote:
> > On Thu, 14 Jun 2001, Ian Roxborough wrote:
> > 
> > > Another fix is to switch and rename the hacked tcl_findLibrary with
> > > the real tcl_findLibrary, so we don't rely on the hack being in
> > > the Tcl version.
> > >
> > > Another fix is to "detect" (if <gdb executablr dir> + gdb-tk.o = true...?)
> > > if we are in the build directory then set the required
> > > *_LIBRARY variables as needed.
> > 
> > I'll vote for losing the hacked tcl_findLibrary, and using some heuristic
> > for determining if we are running in the build dir. Anything to prevent us
> > from modifying Tcl/Tk/tix/itcl/etc.
> 
> I'm finding yet more and more local changes to Tcl to make it play nicely
> with Insight running from the build directory (the ones for launching
> Tcl in tclInitScript.h).
> 
> Is anybody going to mind if I install a script at build time to run
> gdb out of the build directory.  Maybe call it run-insight.sh or something.
> Everything works other than typing ./gdb in the build directory,
> I'm not sure if this is worth all the code changes vs. a 7 line
> shell script.

Why don't we setup things so that running "make gdb" runs the
executable in the build directory. That way, we could set the
TCL_LIBRARY env var before running gdb in the build dir. That
is how tclsh is run out of the build directory. We should stick
with something simple instead of hacking the source code
to support running in the build dir (if possible).
 
Mo DeJong
Red Hat Inc