public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
* Re: insight Digest 14 Jun 2001 22:30:35 -0000 Issue 393
       [not found] <992557835.22758.ezmlm@sources.redhat.com>
@ 2001-06-14 18:43 ` Jim Ingham
  2001-06-15  6:39   ` Fernando Nasser
  0 siblings, 1 reply; 2+ messages in thread
From: Jim Ingham @ 2001-06-14 18:43 UTC (permalink / raw)
  To: insight

Ian


> 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.

If you want to do this, fine...  But you want BOTH "run gdb from the 
build directory" and "debug a version of gdb from the build directory", 
since

gdb run-insight.sh

is probably not going to do what you want...

I actually think that the changes I made to get this all to work are 
good, and SHOULD make it back to the SourceForge Tcl.  The basic 
observation is that as long as you don't move the sources around,  the 
tclConfig.sh files KNOW where all the sources are.  So you should look 
for them (they are VERY likely to be local and easy to find when running 
from the build tree), and not do some dopey groping around a couple 
directories up type heuristics to find the sources - which are not 
guaranteed to be anywhere near the build tree.

I tried to argue this with Brent a couple of years back, but I don't 
think anyone at Scriptics at the time much cared about this, and they 
ALWAYS build in the source tree, so this was not much of an issue for 
them.

But, OTOH, I don't work on this stuff any more, so I am not going to 
commit hari kari no matter what you do...

>
> It looks like it would be a good idea to revisit how Insight is
> being launched, making SN location independant made a lot of things
> easier (I was noticing that if I rename my install dir Insight doesn't
> work any more).  But this is probably outside of the scope the Tcl/Tk
> upgrade.
>

Jim
--
Jim Ingham                                   jingham@apple.com
Developer Tools - gdb
Apple Computer

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: insight Digest 14 Jun 2001 22:30:35 -0000 Issue 393
  2001-06-14 18:43 ` insight Digest 14 Jun 2001 22:30:35 -0000 Issue 393 Jim Ingham
@ 2001-06-15  6:39   ` Fernando Nasser
  0 siblings, 0 replies; 2+ messages in thread
From: Fernando Nasser @ 2001-06-15  6:39 UTC (permalink / raw)
  To: Jim Ingham; +Cc: insight

Thanks for the comments Jim.  You know more of the history of these
things.

Ian,

Now that Tcl is in sourceforge they may be more willing to consider our
changes.  Don't you want to try submitting some of those?  

Of course, this would only help us for 8.4, I guess.  We would have to
use some other solution anyway if we want to use the instaled 8.3 Tcl.
:-(

Fernando




Jim Ingham wrote:
> 
> Ian
> 
> > 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.
> 
> If you want to do this, fine...  But you want BOTH "run gdb from the
> build directory" and "debug a version of gdb from the build directory",
> since
> 
> gdb run-insight.sh
> 
> is probably not going to do what you want...
> 
> I actually think that the changes I made to get this all to work are
> good, and SHOULD make it back to the SourceForge Tcl.  The basic
> observation is that as long as you don't move the sources around,  the
> tclConfig.sh files KNOW where all the sources are.  So you should look
> for them (they are VERY likely to be local and easy to find when running
> from the build tree), and not do some dopey groping around a couple
> directories up type heuristics to find the sources - which are not
> guaranteed to be anywhere near the build tree.
> 
> I tried to argue this with Brent a couple of years back, but I don't
> think anyone at Scriptics at the time much cared about this, and they
> ALWAYS build in the source tree, so this was not much of an issue for
> them.
> 
> But, OTOH, I don't work on this stuff any more, so I am not going to
> commit hari kari no matter what you do...
> 
> >
> > It looks like it would be a good idea to revisit how Insight is
> > being launched, making SN location independant made a lot of things
> > easier (I was noticing that if I rename my install dir Insight doesn't
> > work any more).  But this is probably outside of the scope the Tcl/Tk
> > upgrade.
> >
> 
> Jim
> --
> Jim Ingham                                   jingham@apple.com
> Developer Tools - gdb
> Apple Computer

-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2001-06-15  6:39 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <992557835.22758.ezmlm@sources.redhat.com>
2001-06-14 18:43 ` insight Digest 14 Jun 2001 22:30:35 -0000 Issue 393 Jim Ingham
2001-06-15  6:39   ` Fernando Nasser

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).