Re: Tcl/Tk 8.3 upgrade...

[Keith Seitz <keiths at cygnus dot com>]

On Fri, 15 Jun 2001, Ian Roxborough wrote:

> I bet you they do.  The only adjustment that I made to
> get the gdbtk testsuit running was setting ITK_LIBRARY.
> They are hacks in the current cvs version of Tcl which
> munge out the ITCL/ITK pathes to find the source directory.

Yes, the testsuite should still run, even from the build directory. I went
to great pains to do this. The dejagnu infrastructure will set all the
*_LIBRARY environment variables. AFAIK, this is all that needs to be done.

> The only think that didn't work is running gdbtk from the
> build directory without setting the *_LIBRARY environment
> variables.

Well, I can think of another way to do it using your "run-insight" script
(involving adding to .gdbinit), but I want to see insight decoupled from
gdb proper, and this wouldn't help.  (Remember, we are a bastard project,
which is why we must keep the copyright assigned to Red Hat instead of the
FSF. It's not that we don't want the FSF to use Insight, but FSF insists
that tcl is evil.)

> What I've added will now check to see if gdb has been ran
> from a "bin" directory.  If not and TCL_LIBRARY isn't set,
> then it will set TCL_LIBRARY and then run a short embedded
> Tcl script to set the other *_LIBRARY before going on to
> start Insight.

I don't think this is unreasonable. Ugly maybe, but not unreasonable.

> You could also use this code to try and solve some of gdbtk's
> location independance problems.

Ugh. Configury is really the problem. I'm still in shock over last night's
little introduction to the complexities of gdb/insight configury.

> Is there any chance of major changes over that time?
> When are you planning to split gdb and insight in to
> seperate modules?

With every passing day, I make major changes, but I've got plenty of
battles in gdb-land to overcome before I can commit them. So don't sweat
it. I are a trained professional (TM). :-)

Keith