Re: Tcl/Tk 8.3 upgrade...

[Ian Roxborough <irox at evilpeople dot com>]

On Tue, 12 Jun 2001 18:18:30 -0700 (PDT)
Keith Seitz <keiths@cygnus.com> wrote:
> Are we really replacing the call to tcl_findLibrary in Tcl? Ouch... Well,
> I understand WHY we are doing it (so that we can run from the build
> directory), but there must surely be better ways to do it.

OK, so after some more testing I found that my fix doesn't let you
run Insight from the build directory without setting the environment
variables: GDBTK_LIBRARY, ITCL_LIBRARY, ITK_LIBRARY, TCL_LIBRARY,
TIX_LIBRARY and TK_LIBRARY to point to the respective library directories
in the source tree. (Actually, using the current cvs version
of Tcl/Tk will only need GDBTK_LIBRARY set, due to the extra majic
in tcl_findLibrary will search the source directorys anyway.)

The testsuits run find as they set all the *_LIBRARY variables before
running gdb.

I guess running gdb in the build directory helps speed up development (no
install time).  The simplest fix is to use a script to launch gdb
when running it in the build directory.

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.

If desired we can bring the hacked tcl_findLibrary in the Tcl8.3
version, but I'd like to avoid doing that.

> In either case, I don't like using the name "gdb1.0". If you go this
> route, please use insight1.0 or gdbtk1.0. I am already considering
> "purifying" the gdb repository by taking insight out and teaching gdb how
> to deal with other toplevel UIs.

I used insight1.0 as the replacement name for the gdbtcl directory.

Ian.
-- 
What would Jenna Bush do?